From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Benjamin Poirier <benjamin.poirier@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Helge Deller <deller@gmx.de>, Ian Kent <raven@themaw.net>,
Sven Joachim <svenjoac@gmx.de>,
Nandha Kumar Singaram <nandhakumar.singaram@gmail.com>,
Sumitra Sharma <sumitraartsy@gmail.com>,
Ricardo Lopes <ricardoapl.dev@gmail.com>,
Dan Carpenter <error27@gmail.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-staging@lists.linux.dev,
Manish Chopra <manishc@marvell.com>,
Coiby Xu <coiby.xu@gmail.com>
Subject: Re: [PATCH 0/2] staging: qlge: Remove qlge
Date: Sat, 21 Oct 2023 11:53:07 +0200 [thread overview]
Message-ID: <2023102158-unison-depth-0db6@gregkh> (raw)
In-Reply-To: <20231020124457.312449-1-benjamin.poirier@gmail.com>
On Fri, Oct 20, 2023 at 08:44:55AM -0400, Benjamin Poirier wrote:
> Remove the qlge driver from staging. The TODO file is first updated to
> reflect the current status, in case the removal is later reverted.
Thanks for this, now applied!
greg k-h
prev parent reply other threads:[~2023-10-21 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 12:44 [PATCH 0/2] staging: qlge: Remove qlge Benjamin Poirier
2023-10-20 12:44 ` [PATCH 1/2] staging: qlge: Update TODO Benjamin Poirier
2023-10-21 0:07 ` [PATCH 0/2] staging: qlge: Remove qlge Jakub Kicinski
2023-10-21 9:53 ` Greg Kroah-Hartman [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=2023102158-unison-depth-0db6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=benjamin.poirier@gmail.com \
--cc=coiby.xu@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manishc@marvell.com \
--cc=nandhakumar.singaram@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raven@themaw.net \
--cc=ricardoapl.dev@gmail.com \
--cc=sumitraartsy@gmail.com \
--cc=svenjoac@gmx.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).