All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Satish Kharat <satishkh@cisco.com>
Cc: Leon Romanovsky <leon@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: drop enic maintainer entry for benve
Date: Wed, 18 Feb 2026 16:12:48 -0800	[thread overview]
Message-ID: <20260218161248.1cfbb278@kernel.org> (raw)
In-Reply-To: <20260218182610.1138802-1-satishkh@cisco.com>

On Wed, 18 Feb 2026 10:26:10 -0800 Satish Kharat wrote:
> Christian Benvenuti is no longer involved in the development of the enic driver.
> The <benve@cisco.com> email address is no longer valid. I will send a separate
> patch to update the usnic component.

Please send a combined one. Why would we need a commit per line of
changed MAINTAINERS file.

      reply	other threads:[~2026-02-19  0:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14 14:26 [PATCH] MAINTAINERS: drop enic maintainer entry for benve Satish Kharat
2026-02-14 14:26 ` Satish Kharat via B4 Relay
2026-02-15  7:41 ` Leon Romanovsky
2026-02-18 18:26   ` Satish Kharat
2026-02-19  0:12     ` Jakub Kicinski [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=20260218161248.1cfbb278@kernel.org \
    --to=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=satishkh@cisco.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.