From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Sarah Sharp <sarah.a.sharp@linux•intel.com>
Subject: Re: linux-next: usb tree build failure
Date: Wed, 29 Apr 2009 08:16:18 -0700 [thread overview]
Message-ID: <20090429151618.GD16302@kroah.com> (raw)
In-Reply-To: <20090430010057.d5a98bf9.sfr@canb.auug.org.au>
On Thu, Apr 30, 2009 at 01:00:57AM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> On Wed, 29 Apr 2009 07:15:19 -0700 Greg KH <greg@kroah•com> wrote:
> >
> > They were all posted on the linux-usb mailing list, as they are a new
> > USB controller (for USB 3.0), so they didn't need to be sent to lkml.
> >
> > But yes, the code does still need work, that is known, but a build
> > failure wasn't known :)
>
> This is what I tell maintainers of new trees being integrated into
> linux-next:
>
> "all patches/commits in the tree/series must have been:
>
> posted to a relevant mailing list
> reviewed
> unit tested
> destined for the next merge window (or the current release)
All of these are true for this code.
> *before* they are included. The linux-next tree is for integration
> testing and to lower the impact of conflicts between subsystems in the
> next merge window.
>
> Basically, this should be just what you would send to Linus (or ask him
> to fetch). It is allowed to be rebased if you deem it necessary."
Yes, thanks, I went on the fact that this code has been shown to work,
and is self-contained (new driver). Yes, it will need some work, and
your build log certainly showed that (I already let Sarah know about the
build warnings that I had seen).
I had missed the global names that were not unique, and thank you for
that, I'll go resolve it.
thanks,
greg k-h
next prev parent reply other threads:[~2009-04-29 15:41 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 7:17 linux-next: usb tree build failure Stephen Rothwell
2009-04-29 14:15 ` Greg KH
2009-04-29 15:00 ` Stephen Rothwell
2009-04-29 15:16 ` Greg KH [this message]
2009-04-29 15:18 ` Randy Dunlap
2009-04-29 15:37 ` Greg KH
2009-04-29 15:44 ` Randy Dunlap
2009-04-29 17:44 ` Greg KH
2009-04-29 17:53 ` Randy Dunlap
2009-04-30 16:13 ` Greg KH
2009-04-30 16:27 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2010-02-02 6:10 Stephen Rothwell
2010-02-02 13:53 ` Greg KH
2010-02-02 22:33 ` Stephen Rothwell
2009-08-19 8:34 Stephen Rothwell
2009-08-19 13:52 ` Greg KH
2009-08-19 23:45 ` Greg KH
2009-08-19 23:58 ` Stephen Rothwell
2008-12-22 0:33 Stephen Rothwell
2008-12-22 1:31 ` Greg KH
2008-12-22 2:42 ` Stephen Rothwell
2008-12-22 6:45 ` Sam Ravnborg
2008-12-22 17:26 ` Inaky Perez-Gonzalez
2008-12-22 17:53 ` Sam Ravnborg
2008-12-22 23:37 ` Inaky Perez-Gonzalez
2008-12-23 4:31 ` Greg KH
2008-12-23 4:30 ` Greg KH
2008-12-23 4:31 ` Greg KH
2008-12-23 10:26 ` Inaky Perez-Gonzalez
2008-12-23 17:17 ` Greg KH
2008-12-24 1:07 ` Inaky Perez-Gonzalez
2009-01-05 4:34 ` Greg KH
2009-01-05 5:55 ` Stephen Rothwell
2008-12-29 3:55 ` Stephen Rothwell
2009-01-02 7:27 ` Greg KH
2009-01-03 4:33 ` Stephen Rothwell
2008-11-03 0:36 Stephen Rothwell
2008-11-05 4:47 ` Greg KH
2008-11-05 18:19 ` Mauro Carvalho Chehab
2008-10-14 4:08 Stephen Rothwell
2008-10-14 5:51 ` Alexey Klimov
2008-10-14 17:41 ` Alexey Klimov
2008-10-14 17:26 ` Mauro Carvalho Chehab
2008-10-14 3:59 Stephen Rothwell
2008-10-14 8:24 ` Dmitry
2008-10-14 15:42 ` Dmitry
2008-10-16 16:05 ` Greg KH
2008-10-16 17:27 ` Dmitry Baryshkov
2008-10-16 21:36 ` Dmitry Baryshkov
2008-10-17 0:26 ` Stephen Rothwell
2008-10-17 0:41 ` Dmitry
2008-10-20 18:45 ` Greg KH
2008-08-13 6:37 Stephen Rothwell
2008-08-13 7:33 ` Stephen Rothwell
2008-08-13 14:23 ` Stephen Rothwell
2008-08-14 6:28 ` Stephen Rothwell
2008-08-14 6:54 ` Stephen Rothwell
2008-08-14 12:25 ` Greg KH
2008-08-15 0:16 ` Stephen Rothwell
2008-07-18 1:31 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=20090429151618.GD16302@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sarah.a.sharp@linux$(echo .)intel.com \
--cc=sfr@canb$(echo .)auug.org.au \
/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