linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: Vinod Koul <vkoul@kernel.org>,
	bhupesh.linux@gmail.com,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Jose Abreu <joabreu@synopsys.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Drop unreachable reviewer for Qualcomm ETHQOS ethernet driver
Date: Wed, 31 Jan 2024 15:41:48 -0800	[thread overview]
Message-ID: <20240131154148.00d9d318@kernel.org> (raw)
In-Reply-To: <ual3c4fuuz5trgn2ekklsfeslwvswfjg5nij5epbnuf5mihfay@pp32fs6btwxk>

On Tue, 30 Jan 2024 09:53:22 -0600 Andrew Halaney wrote:
> > Looks like Bhupesh sent the patch changing but never followed up with a
> > v2 for this:
> > lore.kernel.org/r/20230915191600.3410862-1-bhupesh.linux@gmail.com
> > 
> > Would prefer if this is changed to his email (copied him as well)
> >   
> 
> Thanks for finding that! Bhupesh, do you plan on spinning a v2 soon? If
> so I will not send a v2, otherwise I can respin this with your email and
> no .mailmap change.

The lack of response is not inspiring confidence. We can add Bhupesh
back if he wants to be active again..

  reply	other threads:[~2024-01-31 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 17:12 [PATCH] MAINTAINERS: Drop unreachable reviewer for Qualcomm ETHQOS ethernet driver Andrew Halaney
2024-01-30 15:33 ` Vinod Koul
2024-01-30 15:53   ` Andrew Halaney
2024-01-31 23:41     ` Jakub Kicinski [this message]
2024-02-01  0:00 ` patchwork-bot+netdevbpf

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=20240131154148.00d9d318@kernel.org \
    --to=kuba@kernel.org \
    --cc=ahalaney@redhat.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=bhupesh.linux@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=joabreu@synopsys.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vkoul@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).