All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: Tree for November 7
Date: Sat, 8 Nov 2008 20:13:03 +0100	[thread overview]
Message-ID: <200811082013.04066.bzolnier@gmail.com> (raw)
In-Reply-To: <20081108184315.GA9382@x200.localdomain>

On Saturday 08 November 2008, Alexey Dobriyan wrote:
> On Sat, Nov 08, 2008 at 12:57:44PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > On Friday 07 November 2008, Stephen Rothwell wrote:
> > > Changes since 20081106:
> > 
> > The following patch fixes the panic on loopback device registration
> > (patch is an interdiff between old and new version of "net: Guaranetee
> > the proper ordering of the loopback device." fix from Eric).
> > 
> > [ I'm sure this will get fixed in -net tree (if not fixed already)
> >   but at the moment it is needed for linux-next. ]
> 
> This patch alone is a) not enough, and b) davem already pushed out correct
> version.

Well, it was enough to make next-20081107 bootable for me. :-)

However, it seems like the following patch is also neeed by linux-next users:
 http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=commitdiff;h=5d6d480908300a0c0b3be8b58567dfcef62c83a5

[ I also see that it is fixed now but it was actually an overdue mail from
  yesterday and like I said earlier, the sole its purpose was to help people
  trying linux-next kernels (linux-next is not released on weekends so from
  their POV it doesn't really matter if it already got fixed in net-next). ]

Thanks,
Bart

  reply	other threads:[~2008-11-08 19:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  9:54 linux-next: Tree for November 7 Stephen Rothwell
2008-11-07 22:30 ` next-20081107: ia64 vs kvm Alexey Dobriyan
2008-11-08  7:57   ` Zhang, Xiantao
2008-11-09 10:00     ` Avi Kivity
2008-11-07 23:04 ` linux-next: Tree for November 7 Alexey Dobriyan
2008-11-08 11:57 ` Bartlomiej Zolnierkiewicz
2008-11-08 18:43   ` Alexey Dobriyan
2008-11-08 19:13     ` Bartlomiej Zolnierkiewicz [this message]
2008-11-10  6:45 ` KAMEZAWA Hiroyuki
2008-11-10  8:12   ` KAMEZAWA Hiroyuki

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=200811082013.04066.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.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.