From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH] i2c: update for semaphore to mutex conversion of devices
Date: Mon, 8 Mar 2010 18:27:09 -0800 [thread overview]
Message-ID: <20100309022709.GA25756@kroah.com> (raw)
In-Reply-To: <20100309125037.5a218f22.sfr@canb.auug.org.au>
On Tue, Mar 09, 2010 at 12:50:37PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> On Mon, 8 Mar 2010 15:59:53 -0800 Greg KH <greg@kroah.com> wrote:
> >
> > On Tue, Mar 09, 2010 at 10:28:28AM +1100, Stephen Rothwell wrote:
> > > I have been carrying this patch in linux-next for some time and now
> > > mainline needs it.
> >
> > Well, it's not required, but it is nice to have. I didn't merge the
> > "convert the driver core semaphore to a mutex" patch as it was causing
> > too many false-positive lockdep warnings.
>
> Ah, I missed that, sorry.
>
> Strangely, I was assuming that what was in linux-next would get merged :-)
That is normally the case, but when patches are found to have problems,
due to the testing that happens with linux-next, they can then be not
sent to Linus, right?
That's what happened here, we need more infrastructure to be able to
accept them. I see it as a validation that our development model is
working properly that this happened :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-03-09 2:27 UTC|newest]
Thread overview: 11+ 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 [this message]
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:39 ` Jean Delvare
2010-03-09 10:47 ` Stephen Rothwell
2010-03-09 10:47 ` Stephen Rothwell
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=20100309022709.GA25756@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.