From: Greg KH <gregkh@suse.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Need to take dev->sem, do it directly or use wrapper?
Date: Mon, 4 Jan 2010 12:04:36 -0800 [thread overview]
Message-ID: <20100104200436.GA22515@suse.de> (raw)
In-Reply-To: <20100104185023.GA2597@core.coreip.homeip.net>
On Mon, Jan 04, 2010 at 10:50:23AM -0800, Dmitry Torokhov wrote:
> Greg,
>
> I was looking at restructuring serio a bit and rely more on the
> infrastructure in the drivre core now that it is more flexible. It all
> looks good except for one detail - serio provides "reconnect" method
> which allows user to reinitialize a port whithout tearing down its
> children input devices. To properly serialize with probe(), remove() and
> other bus operations I'd need to take dev->sem semaphore. I(s bus code
> allowed to do this? Can I do it directly or we need to add a wrapper
> (like device_serialize_access(dev, bool))?
Adding a wrapper would be best to do.
thanks,
greg k-h
prev parent reply other threads:[~2010-01-04 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 18:50 Need to take dev->sem, do it directly or use wrapper? Dmitry Torokhov
2010-01-04 20:04 ` Greg KH [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=20100104200436.GA22515@suse.de \
--to=gregkh@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.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