From: Matthias Kaehlcke <matthias.kaehlcke@gmail.com>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: gregkh@suse.de, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 1/2] ELAN U132 Host Controller Driver: convert sw_lock to mutex
Date: Fri, 7 Sep 2007 08:14:11 +0200 [thread overview]
Message-ID: <20070907061411.GF3081@traven> (raw)
In-Reply-To: <E1ITPWc-0004rC-Kr@flower>
El Fri, Sep 07, 2007 at 12:08:34AM +0200 Oleg Verych ha dit:
> * Thu, 6 Sep 2007 23:18:15 +0200
>
> []
> > @@ -184,7 +184,7 @@ struct u132_ring {
> > struct u132 {
>
> Subject: [PATCH 1/2] ELAN U132 Host Controller Driver: convert sw_lock to mutex
> []
> > struct list_head u132_list;
> > - struct semaphore sw_lock;
> > + struct mutex sw_lock;
> > struct semaphore scheduler_lock;
>
> Subject: [PATCH 2/2] ELAN U132 Host Controller Driver: convert scheduler_lock t
> []
> > struct list_head u132_list;
> > struct semaphore sw_lock;
> >- struct semaphore scheduler_lock;
> >+ struct mutex scheduler_lock;
>
> Are you sure, you have right patch sequence?
my idea was to sent two independent patches, would it be better to
have one patch based on the other?
--
Matthias Kaehlcke
Linux Application Developer
Barcelona
Insanity: doing the same thing over and over
again and expecting different results
(Albert Einstein)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
next prev parent reply other threads:[~2007-09-07 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 21:09 [PATCH 0/2] Use mutexes instead of semaphores in the ELAN U132 Host Controller Driver Matthias Kaehlcke
2007-09-06 21:18 ` [PATCH 1/2] ELAN U132 Host Controller Driver: convert sw_lock to mutex Matthias Kaehlcke
2007-09-06 22:08 ` Oleg Verych
2007-09-07 6:14 ` Matthias Kaehlcke [this message]
2007-09-06 21:19 ` [PATCH 2/2] ELAN U132 Host Controller Driver: convert scheduler_lock " Matthias Kaehlcke
2007-09-07 13:10 ` Matthias Kaehlcke
2007-09-09 16:41 ` Greg KH
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=20070907061411.GF3081@traven \
--to=matthias.kaehlcke@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=olecom@flower.upol.cz \
/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