All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 7
Date: Thu, 6 Mar 2008 20:39:50 -0800	[thread overview]
Message-ID: <20080307043950.GA669@kroah.com> (raw)
In-Reply-To: <20080307141856.b27d1725.sfr@canb.auug.org.au>

On Fri, Mar 07, 2008 at 02:18:56PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> (tar balls at
> http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).
> 
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log files
> in the Next directory.  Between each merge, the tree was built with
> allmodconfig for both powerpc and x86_64.
> 
> There were a few merge conflicts (trivial) and one build break.  I have
> notified the appropriate people.
> 
> We are up to 44 trees, more are welcome (even if they are currently
> empty).  The influx of new trees has been underwhelming.  Thanks to those
> who have contributed, and to those who haven't, please do.
> 
> Status of my local build tests is at
> http://kisskb.ellerman.id.au/kisskb/branch/9/.  If maintainers want to
> give advice about cross compilers/configs that work, we are always open
> to add more builds.  Build results from today on also include the actual
> compiler version string.
> 
> It looks like this one is going to build fail the same way as yesterday's tree:
> 
> drivers/usb/core/hub.c:633: error: 'struct usb_device' has no member named 'persist_enabled'
> drivers/usb/core/hub.c:719: error: 'struct usb_device' has no member named 'reset_resume'
> 
> for any config with CONFIG_PM disabled.

I have a patch in my to-apply queue for this, so hopefully it will not
happen tomorrow :)

thanks,

greg k-h

  reply	other threads:[~2008-03-07  4:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  3:18 linux-next: Tree for March 7 Stephen Rothwell
2008-03-07  4:39 ` Greg KH [this message]
2008-03-08 10:45 ` linux-next: Tree for March 7: slab corruptions Laurent Riffard
2008-03-08 18:59   ` Balaji Rao
2008-03-09  3:05     ` Greg KH
2008-03-09  8:13       ` Laurent Riffard
  -- strict thread matches above, loose matches on Subject: below --
2011-03-07  7:05 linux-next: Tree for March 7 Stephen Rothwell
2011-03-07 19:05 ` Mariusz Kozlowski
2011-03-07 19:52   ` Narendra_K
2011-03-07 19:52     ` Narendra_K
2011-03-08 20:57     ` Mariusz Kozlowski
2011-03-09 16:45       ` Mariusz Kozlowski

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=20080307043950.GA669@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.