mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@sandisk.com>
To: Bart Van Assche <bvanassche@acm.org>, Bean Huo <beanhuo@iokpp.de>,
	Stanley Jhu <stanleyjhu@google.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] MAINTAINERS: Remove Avri Altman as UFS reviewer
Date: Mon, 5 Oct 2026 07:32:40 +0000	[thread overview]
Message-ID: <BL3PR16MB4473EA8F18B6CE741C6F1EC5E5962@BL3PR16MB4473.namprd16.prod.outlook.com> (raw)
In-Reply-To: <21853b19-d02a-4268-80a7-e457ef813522@acm.org>

> On 10/4/26 3:10 AM, Bean Huo wrote:
> > On Sun, 2026-10-04 at 08:21 +0000, Avri Altman wrote:
> >>
> >>> It was off-list. I asked Avri on Sep 29 about updating the bouncing
> >>> wdc.com address, and he asked to be removed as a reviewer instead.
> >>>
> >>> Avri, could you reply with your Acked-by?
> >> Acked-by: Avri Altman <avri.altman@sandisk.com>
> >>
> >> Stanley thanks - sorry for my late response.
> >> I do feel that the reviewer role is no longer needed for the ufs driver.
> >
> > A sad day for the UFS driver, we’ve just lost a brilliant reviewer!
> 
> Thanks Avri for your numerous high-quality reviews of UFS kernel driver
> patches!
Yo guys - I am not dead.  Just thought that the "reviewer" entry is no longer needed.

Thanks,
Avri

> 
> Bart.

  reply	other threads:[~2026-10-05  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 13:59 Stanley Jhu
2026-10-02  9:14 ` Bean Huo
2026-10-02 13:31 ` Bart Van Assche
2026-10-02 13:41   ` Stanley Jhu
2026-10-04  8:21     ` Avri Altman
2026-10-04 10:10       ` Bean Huo
2026-10-04 22:42         ` Bart Van Assche
2026-10-05  7:32           ` Avri Altman [this message]
2026-10-06  1:36 ` Martin K. Petersen (Oracle)

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=BL3PR16MB4473EA8F18B6CE741C6F1EC5E5962@BL3PR16MB4473.namprd16.prod.outlook.com \
    --to=avri.altman@sandisk.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alim.akhtar@samsung.com \
    --cc=beanhuo@iokpp.de \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanleyjhu@google.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®