From: Greg KH <gregkh@linuxfoundation.org>
To: Tom Van Braeckel <tomvanbraeckel@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, samu.p.onkalo@nokia.com
Subject: Re: [PATCH] misc: pass miscdevice through file's private_data
Date: Tue, 31 Mar 2015 15:19:20 +0200 [thread overview]
Message-ID: <20150331131920.GA6373@kroah.com> (raw)
In-Reply-To: <CAJ7vePBhwBfGeGdQDpH9Tmva7sxhprtk=S9veK=PqdE_dKtumw@mail.gmail.com>
On Tue, Mar 31, 2015 at 03:08:38PM +0200, Tom Van Braeckel wrote:
> >> Wait, didn't this break FUSE? Or was that some other variant of this
> >> patch?
>
> The fix for FUSE is in 4.0-rc5 and linux-next. Btrfs was not affected,
> in the end. All kernel code has been checked for potential regressions.
>
> So in my opinion, the time has come to apply this patch to char-misc so
> it can get some more testing in linux-next...
What is "this patch"? I don't see it in the email :)
Please resend it, I don't have it in my patch queue anymore.
thanks,
greg k-h
next prev parent reply other threads:[~2015-03-31 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:08 [PATCH] Misc: pass miscdevice through file's private_data Tom Van Braeckel
2014-12-04 21:13 ` Greg KH
2014-12-04 23:01 ` Tom Van Braeckel
2014-12-04 23:29 ` Greg KH
2014-12-05 4:37 ` [PATCH] misc: " Tom Van Braeckel
2015-01-09 23:02 ` Greg KH
2015-01-11 15:44 ` Tom Van Braeckel
2015-03-23 12:59 ` always assign miscdevice to file->private_data Martin Kepplinger
2015-03-23 12:59 ` [PATCH 1/4] char: misc: document behaviour of open() Martin Kepplinger
2015-03-23 12:59 ` [PATCH 2/4] fbdev: pxa3xx-gcu: remove redundant implementation " Martin Kepplinger
2015-03-23 12:59 ` [PATCH 3/4] fs: btrfs: set file->private data NULL after open() because we depend on it Martin Kepplinger
2015-03-23 12:59 ` [PATCH 4/4] lguest: explicitly set miscdevice's private_data NULL Martin Kepplinger
2015-03-31 13:08 ` [PATCH] misc: pass miscdevice through file's private_data Tom Van Braeckel
2015-03-31 13:19 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-31 14:39 Tom Van Braeckel
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=20150331131920.GA6373@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=samu.p.onkalo@nokia.com \
--cc=tomvanbraeckel@gmail.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