From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jean Delvare <khali@linux-fr•org>
Cc: Linus <torvalds@linux-foundation•org>,
Andrew Morton <akpm@linux-foundation•org>,
Greg KH <greg@kroah•com>, LKML <linux-kernel@vger•kernel.org>,
linux-next@vger•kernel.org
Subject: Re: [PATCH] i2c: update for semaphore to mutex conversion of devices
Date: Tue, 9 Mar 2010 21:47:02 +1100 [thread overview]
Message-ID: <20100309214702.307a1f5a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100309113950.48be08a1@hyperion.delvare>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi Jean,
On Tue, 9 Mar 2010 11:39:50 +0100 Jean Delvare <khali@linux-fr•org> wrote:
>
> > Thanks. The include of mutex.h is not actually needed yet as Greg didn't
> > send the semaphore to mutex change to Linus due to other issues.
>
> It will never be needed, and I also removed the include of semaphore.h.
> The beauty of the new API is that it hides the implementation details
> from the caller!
Yeah, except it scares me a little since device.h currently does not
directly include semaphore.h and the patch that changes the semaphore to
a mutex does not include mutex.h in device.h either ...
I guess that is a problem for Greg, though.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-03-09 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 23:28 [PATCH] i2c: update for semaphore to mutex conversion of devices Stephen Rothwell
2010-03-08 23:59 ` Greg KH
2010-03-09 1:50 ` Stephen Rothwell
2010-03-09 2:27 ` Greg KH
2010-03-09 16:04 ` Peter Zijlstra
2010-03-09 8:25 ` Jean Delvare
2010-03-09 10:36 ` Stephen Rothwell
2010-03-09 10:39 ` Jean Delvare
2010-03-09 10:47 ` Stephen Rothwell [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=20100309214702.307a1f5a.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=khali@linux-fr$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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