All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Driver core: add new device to bus's list before probing
Date: Fri, 31 Jul 2009 09:41:59 -0700	[thread overview]
Message-ID: <20090731164159.GA25624@kroah.com> (raw)
In-Reply-To: <ac3eb2510907310930h2e5978een68341c15024aec30@mail.gmail.com>

On Fri, Jul 31, 2009 at 12:30:03PM -0400, Kay Sievers wrote:
> On Fri, Jul 31, 2009 at 12:05, Greg KH<greg@kroah.com> wrote:
> > On Thu, Jul 30, 2009 at 04:57:06PM -0400, Kay Sievers wrote:
> >> On Thu, Jul 30, 2009 at 15:27, Alan Stern<stern@rowland.harvard.edu> wrote:
> 
> >> > Kay, do you want this merged into 2.6.31 or are you okay with waiting
> >> > for 2.6.32-rc1?  It changes a major core routine.  On the other hand,
> >> > the problem it fixes does affect real users.
> >>
> >> I think it should go into -next and we wait a few days. It seems like
> >> the proper fix, but we should make sure, we didn't miss something.
> >>
> >> After that, it would be nice if we can get that into 2.6.31, as we
> >> have several problems already, which are likely solved by this.
> >
> > But as this isn't a regression (it's how things always have worked,
> > right?),
> 
> Yeah, that sounds right, but I guess we have just been the needed bit
> slower in the past, and with the recent speedups I would expect more
> cases to uncover this issue.
> 
> > I'm a bit leary of pushing it to .31 right now, so late in the
> > release cycle.  How about it goes to Linus for .32, and we backport it
> > to -stable if it looks ok?
> 
> Sure, sounds fine too.
> 
> Would be good though to have it in -next soon. Three major distros are
> preparing a new distro release at the moment, and they will likely
> need to add that to their kernel to make this issue, USB firmware
> loading, and similar things working again.

It will show up in the next linux-next release.

thanks,

greg k-h

      reply	other threads:[~2009-07-31 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 19:27 [PATCH] Driver core: add new device to bus's list before probing Alan Stern
2009-07-30 20:57 ` Kay Sievers
2009-07-31 16:05   ` Greg KH
2009-07-31 16:30     ` Kay Sievers
2009-07-31 16:41       ` 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=20090731164159.GA25624@kroah.com \
    --to=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.