From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Roman Bolshakov <r.bolshakov@yadro.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Anil Gurumurthy <anil.gurumurthy@qlogic.com>,
Sudarsana Kalluru <sudarsana.kalluru@qlogic.com>,
linux-spdx@vger.kernel.org, linux-kernel@vger.kernel.org,
GR-QLogic-Storage-Upstream@marvell.com,
Arun Easi <aeasi@marvell.com>
Subject: Re: [PATCH] MAINTAINERS: orphan sections with qlogic.com group alias
Date: Fri, 28 Aug 2020 11:39:01 -0400 [thread overview]
Message-ID: <yq1h7smkcqc.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2008281524360.11562@felia> (Lukas Bulwahn's message of "Fri, 28 Aug 2020 15:30:44 +0200 (CEST)")
Lukas,
> So, if these drivers are not orphans, you can answer Thomas Gleixner's
> original email from 2019. If you can quickly ack that patch set, I am
> happy to do the donkey work to get this apply nicely on the current
> master (please CC me on that response).
This is the first I hear of this since the patches weren't CC:ed to
linux-scsi. And not all of these changes pertain to storage drivers but
to networking so I am also not sure that mails sent to the above Storage
alias would have ended up in the right place.
But we'll get this fixed up. Reaching out to our contacts at Marvell.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-08-28 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 7:08 [PATCH] MAINTAINERS: orphan sections with qlogic.com group alias Lukas Bulwahn
2020-08-28 9:17 ` Roman Bolshakov
2020-08-28 10:00 ` Greg Kroah-Hartman
2020-08-28 13:30 ` Lukas Bulwahn
2020-08-28 15:02 ` James Bottomley
2020-08-28 15:28 ` Lukas Bulwahn
2020-08-28 15:38 ` James Bottomley
2020-08-28 15:39 ` Martin K. Petersen [this message]
2020-08-28 15:46 ` Lukas Bulwahn
2020-09-08 6:58 ` [EXT] " Arun Easi
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=yq1h7smkcqc.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=aeasi@marvell.com \
--cc=anil.gurumurthy@qlogic.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=r.bolshakov@yadro.com \
--cc=sudarsana.kalluru@qlogic.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