From: Randy Dunlap <randy.dunlap@oracle•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 October 14
Date: Wed, 14 Oct 2009 08:55:15 -0700 [thread overview]
Message-ID: <20091014085515.f40067c1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091014163445.f0441473.sfr@canb.auug.org.au>
On Wed, 14 Oct 2009 16:34:45 +1100 Stephen Rothwell wrote:
> Changes since 20091013:
>
> Undropped tree: i7core_edac
>
> My fixes tree contains a build fix for powerpc/kvm.
>
> The pci tree gained a conflict against Linus' tree.
>
> The kbuild tree gained a build failure that required me to remove
> include/asm/asm-offsets.h from my object tree.
>
> The net tree lost its build failure.
>
> The percpu tree lost its build failure.
>
> The tty tree still had a build failure for which I reverted a commit.
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ). If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one. You should use "git fetch" as mentioned in the FAQ on the wiki
> (see below).
Hi Stephen,
Where are today's .bz2 file and the .sign files?
and when did pub/kernel/people/sfr/linux-next/ disappear?
The kernel.org/kdist/finger_banner file now reports:
The latest linux-next version of the Linux kernel is: next-20091013
instead of 20091014.
---
~Randy
next prev parent reply other threads:[~2009-10-14 15:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 5:34 linux-next: Tree for October 14 Stephen Rothwell
2009-10-14 15:55 ` Randy Dunlap [this message]
2009-10-14 21:12 ` Stephen Rothwell
2009-10-14 22:10 ` [PATCH -next] ia64/sn: fix percpu warnings Randy Dunlap
2009-10-15 1:33 ` Tejun Heo
2009-10-26 18:24 ` Tony Luck
2009-10-26 23:35 ` Luck, Tony
2009-10-28 15:03 ` Tejun Heo
2009-10-28 16:24 ` Luck, Tony
2009-10-28 16:37 ` Tejun Heo
2009-10-28 16:58 ` Luck, Tony
2009-10-28 22:23 ` Luck, Tony
2009-10-29 14:43 ` Tejun Heo
2009-10-29 15:43 ` Tejun Heo
2009-10-30 16:05 ` Jan Beulich
2009-10-14 22:10 ` [PATCH -next] kvm: fix ia64 printk formats Randy Dunlap
2009-10-15 2:32 ` Zhang, Xiantao
2009-10-15 1:17 ` [PATCH -next] vmxnet: fix 2 build problems Randy Dunlap
2009-10-15 2:00 ` [Pv-drivers] " Bhavesh Davda
2009-10-15 3:39 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-10-14 4:26 linux-next: Tree for October 14 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=20091014085515.f40067c1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--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