From: Greg KH <gregkh@linuxfoundation.org>
To: "Buddhabhatti, Jay" <jay.buddhabhatti@amd.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
"Shah, Tanmay" <tanmay.shah@amd.com>,
"Manne, Nava kishore" <nava.kishore.manne@amd.com>,
"Levinsky, Ben" <ben.levinsky@amd.com>,
"robh@kernel.org" <robh@kernel.org>,
"marex@denx.de" <marex@denx.de>,
"Shaikh, Izhar Ameer" <izhar.ameer.shaikh@amd.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"ruanjinjie@huawei.com" <ruanjinjie@huawei.com>,
"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Kannan, Arun Balaji" <arun.balaji.kannan@amd.com>
Subject: Re: [PATCH v2 6/6] drivers: soc: xilinx: update maintainer of event manager driver
Date: Thu, 5 Oct 2023 16:10:55 +0200 [thread overview]
Message-ID: <2023100528-dubbed-parole-0544@gregkh> (raw)
In-Reply-To: <DM6PR12MB4465D25826A74C22B3FC4C1F9DCAA@DM6PR12MB4465.namprd12.prod.outlook.com>
On Thu, Oct 05, 2023 at 02:09:39PM +0000, Buddhabhatti, Jay wrote:
> Hi Greg,
>
> > -----Original Message-----
> > From: Simek, Michal <michal.simek@amd.com>
> > Sent: Wednesday, October 4, 2023 8:05 PM
> > To: Greg KH <gregkh@linuxfoundation.org>
> > Cc: Buddhabhatti, Jay <jay.buddhabhatti@amd.com>; Shah, Tanmay
> > <tanmay.shah@amd.com>; Manne, Nava kishore
> > <nava.kishore.manne@amd.com>; Levinsky, Ben <ben.levinsky@amd.com>;
> > robh@kernel.org; dhaval.r.shah@amd.com; marex@denx.de; Shaikh, Izhar
> > Ameer <izhar.ameer.shaikh@amd.com>; arnd@arndb.de;
> > ruanjinjie@huawei.com; mathieu.poirier@linaro.org; linux-
> > kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org
> > Subject: Re: [PATCH v2 6/6] drivers: soc: xilinx: update maintainer of event
> > manager driver
> >
> >
> >
> > On 10/4/23 15:47, Greg KH wrote:
> > > On Wed, Oct 04, 2023 at 03:16:15PM +0200, Michal Simek wrote:
> > >>
> > >>
> > >> On 10/4/23 14:17, Greg KH wrote:
> > >>> On Wed, Oct 04, 2023 at 02:41:16AM -0700, Jay Buddhabhatti wrote:
> > >>>> Added Michal as a maintainer of event manager driver as Abhyuday is
> > >>>> no longer in AMD-Xilinx.
> > >>>>
> > >>>> Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
> > >>>> Acked-by: Michal Simek <michal.simek@amd.com>
> > >>>> ---
> > >>>> MAINTAINERS | 2 +-
> > >>>> 1 file changed, 1 insertion(+), 1 deletion(-)
> > >>>>
> > >>>> diff --git a/MAINTAINERS b/MAINTAINERS index
> > >>>> 35977b269d5e..f36fefd7032b 100644
> > >>>> --- a/MAINTAINERS
> > >>>> +++ b/MAINTAINERS
> > >>>> @@ -23672,7 +23672,7 @@ F:
> > Documentation/devicetree/bindings/net/can/xilinx,can.yaml
> > >>>> F: drivers/net/can/xilinx_can.c
> > >>>> XILINX EVENT MANAGEMENT DRIVER
> > >>>> -M: Abhyuday Godhasara <abhyuday.godhasara@xilinx.com>
> > >>>> +M: Michal Simek <michal.simek@amd.com>
> > >>>
> > >>> For obvious reasons, we need an ack from Abhyuday.
> > >>
> > >> He no longer works for Xilinx/AMD but I have asked him on side
> > >> channel to reply and let's see if this is going to happen or not.
> > >
> > > Mantainerships follow people, not companies, so if he wants to keep
> > > being the maintainer, he can be, there's no requirement for him to
> > > step down.
> >
> > No doubt about it but normally in these cases people send a patch to start to
> > use their new email address which is what didn't happen for quite a long time
> > in this case.
> > I am definitely happy to wait some time if he reacts but if there is no reaction
> > for some time we should fix it.
>
> [Jay] I got information that Abhyuday is aware about this, but he is not going to react on it.
So I guess they want to remain the maintainer? That's fine, but a new
email address for them is probably wanted if this one currently bounces.
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-05 15:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 9:41 [PATCH v2 0/6] update for versal net platform Jay Buddhabhatti
2023-10-04 9:41 ` [PATCH v2 1/6] firmware: xilinx: Update firmware call interface to support additional arg Jay Buddhabhatti
2023-10-04 12:14 ` Greg KH
2023-10-04 9:41 ` [PATCH v2 2/6] firmware: xilinx: Expand feature check to support all PLM modules Jay Buddhabhatti
2023-10-04 11:30 ` Michal Simek
2023-10-04 9:41 ` [PATCH v2 3/6] firmware: xilinx: Register event manager driver Jay Buddhabhatti
2023-10-04 9:41 ` [PATCH v2 4/6] drivers: soc: xilinx: Fix error message on SGI registration failure Jay Buddhabhatti
2023-10-04 12:15 ` Greg KH
2023-10-04 12:48 ` Buddhabhatti, Jay
2023-10-04 12:51 ` Greg KH
2023-10-04 9:41 ` [PATCH v2 5/6] firmware: zynqmp: Add support to handle IPI CRC failure Jay Buddhabhatti
2023-10-04 9:41 ` [PATCH v2 6/6] drivers: soc: xilinx: update maintainer of event manager driver Jay Buddhabhatti
2023-10-04 12:17 ` Greg KH
2023-10-04 13:16 ` Michal Simek
2023-10-04 13:47 ` Greg KH
2023-10-04 14:34 ` Michal Simek
2023-10-05 14:09 ` Buddhabhatti, Jay
2023-10-05 14:10 ` Greg KH [this message]
2023-10-06 5:15 ` Buddhabhatti, Jay
2023-10-04 11:31 ` [PATCH v2 0/6] update for versal net platform Michal Simek
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=2023100528-dubbed-parole-0544@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=arun.balaji.kannan@amd.com \
--cc=ben.levinsky@amd.com \
--cc=izhar.ameer.shaikh@amd.com \
--cc=jay.buddhabhatti@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@amd.com \
--cc=nava.kishore.manne@amd.com \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=tanmay.shah@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