From: Greg KH <gregkh@linuxfoundation.org>
To: Mandeep Sandhu <mandeep.sandhu@cyaninc.com>
Cc: hjk@hansjkoch.de, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/4] staging: uio: Simplify the lifetime logic of struct uio_device.
Date: Fri, 9 Jan 2015 15:27:12 -0800 [thread overview]
Message-ID: <20150109232712.GA1878@kroah.com> (raw)
In-Reply-To: <1418759544-2610-2-git-send-email-mandeep.sandhu@cyaninc.com>
On Tue, Dec 16, 2014 at 11:52:21AM -0800, Mandeep Sandhu wrote:
> Embed struct device into struct uio_device, and use
> the refcounting and the release method of struct device
> to control struct uio_device.
>
> This allows device_create and device_destroy to be replaced
> with the more standard device_register and device_unregister,
> and allows the struct device reference count to act as a
> reference count on struct idev as well.
>
> Tested-by: Mandeep Sandhu <mandeep.sandhu@cyaninc.com>
> Signed-off-by: Mandeep Sandhu <mandeep.sandhu@cyaninc.com>
> ---
> drivers/uio/uio.c | 41 ++++++++++++++++++++++++++---------------
> include/linux/uio_driver.h | 3 ++-
> 2 files changed, 28 insertions(+), 16 deletions(-)
The subject makes no sense, this has nothing to do with the staging tree
:(
Please fix up and resend this series.
thanks,
greg k-h
next prev parent reply other threads:[~2015-01-09 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 19:52 [PATCH 0/4] uio hotplug support Mandeep Sandhu
2014-12-16 19:52 ` [PATCH 1/4] staging: uio: Simplify the lifetime logic of struct uio_device Mandeep Sandhu
2015-01-09 23:27 ` Greg KH [this message]
2015-01-09 23:36 ` Mandeep Sandhu
2015-01-09 23:45 ` Greg KH
2014-12-16 19:52 ` [PATCH 2/4] staging: uio: Remove unused uio_info mmap method Mandeep Sandhu
2014-12-16 19:52 ` [PATCH 3/4] staging: libunload: A library to help remove open files Mandeep Sandhu
2014-12-16 19:52 ` [PATCH 4/4] staging: uio: Implement hotunplug support, using libunload Mandeep Sandhu
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=20150109232712.GA1878@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mandeep.sandhu@cyaninc.com \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).