From: Johannes Berg <johannes@sipsolutions.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
John Linville <linville@tuxdriver.com>,
LKML <linux-kernel@vger.kernel.org>,
Bill Nottingham <notting@redhat.com>,
linux-wireless@vger.kernel.org
Subject: Re: removal of sysfs wext extension broke on F16
Date: Fri, 16 Nov 2012 21:36:44 +0100 [thread overview]
Message-ID: <1353098204.9490.21.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1353098137.9490.20.camel@jlt4.sipsolutions.net> (sfid-20121116_213518_404111_CB0441EC)
On Fri, 2012-11-16 at 21:35 +0100, Johannes Berg wrote:
> On Fri, 2012-11-16 at 10:20 -0800, Linus Torvalds wrote:
> > On Tue, Nov 13, 2012 at 12:27 AM, Johannes Berg
> > <johannes@sipsolutions.net> wrote:
> > >
> > > Should I revert it and send it in my next pull request?
> >
> > Please do. Or perhaps we could just add the directory back, without
> > the actual entries, if that is sufficient..
>
> Yeah, that does seem to be sufficient, I'll queue up the patch below.
Err, no, wishful thinking. I need a *little* bit more for sysfs to work.
johannes
next prev parent reply other threads:[~2012-11-16 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPM=9twSHBet=vDY9q4BXKv7ZUPR-eme75tOzxrWf6Bsp4MMkw@mail.gmail.com>
[not found] ` <1352795227.9466.8.camel@jlt4.sipsolutions.net>
[not found] ` <CA+55aFw8Rx6TScXV_nsh4EFeCDTxsjn9mJPqo8VzPhbG9jC5Fw@mail.gmail.com>
2012-11-16 20:35 ` removal of sysfs wext extension broke on F16 Johannes Berg
2012-11-16 20:36 ` Johannes Berg [this message]
2012-11-16 20:39 ` Johannes Berg
2012-11-16 22:32 ` Sven-Haegar Koch
2012-11-17 10:32 ` Julian Calaby
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=1353098204.9490.21.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=notting@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox