public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Katakam@ci.codeaurora.org, Harini <harini.katakam@amd.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	pabeni@redhat.com, esben@geanix.com, jsc@umbraculum.org,
	christophe.jaillet@wanadoo.fr, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, harinikatakamlinux@gmail.com,
	michal.simek@amd.com, radhey.shyam.pandey@amd.com
Subject: Re: [PATCH net-next] MAINTAINERS: Add an obsolete entry for LL TEMAC driver
Date: Thu, 28 Sep 2023 14:10:23 +0000	[thread overview]
Message-ID: <169591022321.7456.1928532972585403523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230920115047.31345-1-harini.katakam@amd.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Wed, 20 Sep 2023 17:20:47 +0530 you wrote:
> LL TEMAC IP is no longer supported. Hence add an entry marking the
> driver as obsolete.
> 
> Signed-off-by: Harini Katakam <harini.katakam@amd.com>
> ---
> This is an old driver with no bindings doc and hence the maintainers
> entry does not contain a link to documentation.
> 
> [...]

Here is the summary with links:
  - [net-next] MAINTAINERS: Add an obsolete entry for LL TEMAC driver
    https://git.kernel.org/netdev/net-next/c/19f5eef8bf73

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2023-09-28 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 11:50 [PATCH net-next] MAINTAINERS: Add an obsolete entry for LL TEMAC driver Harini Katakam
2023-09-28 14:10 ` patchwork-bot+netdevbpf [this message]
2023-09-28 14:46 ` esben
2023-09-29  6:06   ` Michal Simek
2023-10-04 14:46     ` Jakub Kicinski
2023-10-05 13:12       ` Katakam, Harini

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=169591022321.7456.1928532972585403523.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Katakam@ci.codeaurora.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=esben@geanix.com \
    --cc=harini.katakam@amd.com \
    --cc=harinikatakamlinux@gmail.com \
    --cc=jsc@umbraculum.org \
    --cc=kuba@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox