From: <subash.a.kasiviswanathan@oss.qualcomm.com>
To: <netdev-bot+sinfo@kernel.org>
Cc: <sean.tranchetti@oss.qualcomm.com>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@kernel.org>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH net v4] net: qualcomm: rmnet: Update MTU handling during format changes
Date: Sun, 8 Nov 2026 01:11:58 -0700 [thread overview]
Message-ID: <000801dd6f58$d38f1e00$7aad5a00$@oss.qualcomm.com> (raw)
In-Reply-To: <179412493254.488859.5909018726402609409@kernel.org>
> -----Original Message-----
> From: netdev-bot+sinfo@kernel.org <netdev-bot+sinfo@kernel.org>
> Sent: Sunday, November 8, 2026 1:02 AM
> To: Subash Abhinov Kasiviswanathan
> <subash.a.kasiviswanathan@oss.qualcomm.com>
> Cc: sean.tranchetti@oss.qualcomm.com; andrew+netdev@lunn.ch;
> davem@davemloft.net; edumazet@kernel.org; kuba@kernel.org;
> pabeni@redhat.com; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH net v4] net: qualcomm: rmnet: Update MTU handling
> during format changes
>
> Hi!
>
> This is an automated message. This series looks like a fix, but its commit
> messages seem to be missing some information:
>
> - Whether the issue was actually triggered, or is only theoretical
> (e.g. found by code inspection). If it was triggered please include
> the symptoms, like the stack trace or error messages.
>
> - What hardware the change was tested on. For driver fixes please
> mention the device (and if relevant firmware version) used for
> testing, or say that the change was not tested on real hardware.
>
> Please do not repost the series just to address the above. Instead, reply to this
> email with the missing information, so that reviewers can take it into account.
> If the series needs another revision for other reasons, please include the
> information in the commit messages then.
>
> The evaluation is done by an LLM so it may be wrong, if you think that is the
> case please reply and explain.
The changes in the patch are addressing the code review comments from Sashiko and not tested on real hardware.
prev parent reply other threads:[~2026-11-08 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 7:57 Subash Abhinov Kasiviswanathan
2026-11-08 8:02 ` netdev-bot+sinfo
2026-11-08 8:11 ` subash.a.kasiviswanathan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000801dd6f58$d38f1e00$7aad5a00$@oss.qualcomm.com' \
--to=subash.a.kasiviswanathan@oss.qualcomm.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.tranchetti@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®