From: Jarek Poplawski <jarkao2@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>, Dave Young <hidave.darkstar@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 01/12] Use mutex instead of semaphore in driver core
Date: Wed, 2 Jan 2008 13:39:38 +0100 [thread overview]
Message-ID: <20080102123938.GA3476@ff.dom.local> (raw)
In-Reply-To: <20080102070008.GA31343@suse.de>
On 02-01-2008 08:00, Greg KH wrote:
...
> If no one has noticed any issues in this area, [...]
...Could also mean there are hidden issues, so it doesn't look like
very convincing argument.
...Unless after the change there will be found no hidden issues,
then, of course, it looks like convincing enough.
Regards,
Jarek P.
next prev parent reply other threads:[~2008-01-02 12:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 1:01 [PATCH 01/12] Use mutex instead of semaphore in driver core Dave Young
2007-12-29 1:29 ` Peter Zijlstra
2007-12-29 1:36 ` Dave Young
2007-12-29 1:40 ` Dave Young
2007-12-29 1:42 ` Peter Zijlstra
2007-12-29 1:52 ` Dave Young
2007-12-29 1:57 ` Peter Zijlstra
2007-12-29 2:03 ` Dave Young
2007-12-29 2:36 ` Dave Young
2007-12-29 4:42 ` Greg KH
2007-12-29 5:06 ` Dave Young
2007-12-29 7:07 ` Dave Young
2007-12-29 17:07 ` Greg KH
2008-01-02 0:54 ` Dave Young
2008-01-02 5:18 ` Greg KH
2008-01-02 5:25 ` David Miller
2008-01-02 7:00 ` Greg KH
2008-01-02 7:52 ` David Miller
2008-01-02 12:39 ` Jarek Poplawski [this message]
2008-01-02 13:12 ` Jarek Poplawski
2008-01-02 16:08 ` Alan Stern
2008-01-03 1:00 ` Dave Young
2008-01-02 5:37 ` Dave Young
2007-12-29 22:01 ` Alan Stern
2007-12-30 6:42 ` David Brownell
2007-12-30 12:13 ` Peter Zijlstra
2008-01-08 16:54 ` Jiri Kosina
2008-01-02 0:58 ` Dave Young
2008-01-02 16:06 ` Alan Stern
2008-01-05 9:30 ` Andrew Morton
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=20080102123938.GA3476@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peterz@infradead.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