From: Jakub Kicinski <kuba@kernel.org>
To: "Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>
Cc: "Gupta, Suraj" <Suraj.Gupta2@amd.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"Simek, Michal" <michal.simek@amd.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"git (AMD-Xilinx)" <git@amd.com>,
"Katakam, Harini" <harini.katakam@amd.com>
Subject: Re: [PATCH net-next] net: axienet: Fix kernel doc warnings
Date: Thu, 7 Mar 2024 17:09:42 -0800 [thread overview]
Message-ID: <20240307170942.6ada3f79@kernel.org> (raw)
In-Reply-To: <MN0PR12MB59536E9DFE0751049F15C1A6B7202@MN0PR12MB5953.namprd12.prod.outlook.com>
On Thu, 7 Mar 2024 16:34:35 +0000 Pandey, Radhey Shyam wrote:
> > Signed-off-by: Suraj Gupta <suraj.gupta2@amd.com>
>
> Reviewed-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Hi, FWIW the patch itself never made it to any kernel mailing list:
https://lore.kernel.org/all/20240306091921.8665-1-suraj.gupta2@amd.com/
you may need to resend
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: "Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>
Cc: "Gupta, Suraj" <Suraj.Gupta2@amd.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"Simek, Michal" <michal.simek@amd.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"git (AMD-Xilinx)" <git@amd.com>,
"Katakam, Harini" <harini.katakam@amd.com>
Subject: Re: [PATCH net-next] net: axienet: Fix kernel doc warnings
Date: Thu, 7 Mar 2024 17:09:42 -0800 [thread overview]
Message-ID: <20240307170942.6ada3f79@kernel.org> (raw)
In-Reply-To: <MN0PR12MB59536E9DFE0751049F15C1A6B7202@MN0PR12MB5953.namprd12.prod.outlook.com>
On Thu, 7 Mar 2024 16:34:35 +0000 Pandey, Radhey Shyam wrote:
> > Signed-off-by: Suraj Gupta <suraj.gupta2@amd.com>
>
> Reviewed-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Hi, FWIW the patch itself never made it to any kernel mailing list:
https://lore.kernel.org/all/20240306091921.8665-1-suraj.gupta2@amd.com/
you may need to resend
next prev parent reply other threads:[~2024-03-08 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306091921.8665-1-suraj.gupta2@amd.com>
2024-03-07 16:34 ` [PATCH net-next] net: axienet: Fix kernel doc warnings Pandey, Radhey Shyam
2024-03-07 16:34 ` Pandey, Radhey Shyam
2024-03-08 1:09 ` Jakub Kicinski [this message]
2024-03-08 1:09 ` Jakub Kicinski
2024-03-13 18:08 ` Gupta, Suraj
2024-03-13 18:08 ` Gupta, Suraj
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=20240307170942.6ada3f79@kernel.org \
--to=kuba@kernel.org \
--cc=Suraj.Gupta2@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.