From: Phillip Potter <phil@philpotter.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Larry Finger <Larry.Finger@lwfinger.net>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-staging@lists.linux.dev
Subject: Re: [GIT PULL] Staging / IIO driver changes for 5.15-rc1
Date: Thu, 2 Sep 2021 23:39:49 +0100 [thread overview]
Message-ID: <YTFStUtOAFTazKSi@equinox> (raw)
In-Reply-To: <CAHk-=whzVVzA5Ng0BUZOvhxEjQiopjwWM5KQDhh6-dWKbD_=vA@mail.gmail.com>
On Wed, Sep 01, 2021 at 02:28:02PM -0700, Linus Torvalds wrote:
> On Wed, Sep 1, 2021 at 2:00 PM Phillip Potter <phil@philpotter.co.uk> wrote:
> >
> > I left this code in when I wrote ae7471cae00a ("staging: r8188eu: remove
> > rtw_ioctl function") with the intention of modifying and reconnecting,
> > once the changes to struct net_device_ops made their way into the
> > staging tree.
>
> Oh, ok. That explains why the dead code existed.
>
> Yeah, I guess y9ou can resurrect it now with the new siocdevprivate model.
>
> I actually ended up doing that first as part of the merge, until I
> noticed that the code wasn't connected in the staging tree at all and
> then decided to undo my merge and just remove the dead code.
>
> Linus
Dear Linus,
Many thanks, I'll get that done. Have a great Friday/weekend.
Regards,
Phil
next prev parent reply other threads:[~2021-09-02 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 14:17 [GIT PULL] Staging / IIO driver changes for 5.15-rc1 Greg KH
2021-09-01 16:49 ` Linus Torvalds
2021-09-01 20:59 ` Phillip Potter
2021-09-01 21:28 ` Linus Torvalds
2021-09-02 22:39 ` Phillip Potter [this message]
2021-09-01 16:52 ` pr-tracker-bot
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=YTFStUtOAFTazKSi@equinox \
--to=phil@philpotter.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.