public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dave Hansen <haveblue@us.ibm.com>, Greg KH <gregkh@suse.de>
Subject: Re: linux-next: usb tree fix (Was: Re: linux-next: Tree for July 29)
Date: Wed, 30 Jul 2008 21:38:47 +0200	[thread overview]
Message-ID: <200807302138.47972.bzolnier@gmail.com> (raw)
In-Reply-To: <20080730110554.9bea652b.sfr@canb.auug.org.au>

On Wednesday 30 July 2008, Stephen Rothwell wrote:
> Hi Bart,
> 
> On Tue, 29 Jul 2008 18:25:14 +0200 Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> >
> > I keep reverting commit 0e3638d1e04040121af00195f7e4628078246489 ("warn
> > when statically-allocated kobjects are used") with each linux-next release
> > to make it work on my x86_32 laptop (http://lkml.org/lkml/2008/7/19/114).
> > 
> > Depending on the day I either forget to revert it on a first try or (lead by
> > incurable optimism) I don't try to revert it in hope that it was fixed.
> > 
> > Unfortunately the result is always the same cursing-during-qemu-test-run
> > -> git-revert -> recompile cycle and a needless time loss.
> > 
> > Could we have some action taken please?
> 
> I have reverted that commit from linux-next today (its id has changed)
> and will do so until Greg or Dave tells me it has been fixed.  To make
> life easier for me, Greg, it would be nice if you removed it from your
> series until that time.

Thanks but since now there is a fix (even two!) for the issue and Dave's
patch has the value of catching real bugs maybe we could have one of the
fixes in linux-next instead of revert?

PS ironically today's linux-next broke xorg for me... call me lucky...

Bart

      reply	other threads:[~2008-07-30 19:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  7:23 linux-next: Tree for July 29 Stephen Rothwell
2008-07-29  7:48 ` Fernando Luis Vázquez Cao
2008-07-29 14:45 ` Dominik Brodowski
2008-08-03 14:56   ` Stephen Rothwell
2008-08-04  7:58     ` Dominik Brodowski
2008-07-29 16:25 ` Bartlomiej Zolnierkiewicz
2008-07-29 18:16   ` Greg KH
2008-07-29 20:49     ` Hugh Dickins
2008-07-30  4:48       ` Greg KH
2008-07-30  7:06         ` Bernhard Walle
2008-07-30  9:19           ` Andrew Morton
2008-07-30 19:27             ` Bartlomiej Zolnierkiewicz
2008-07-30 20:04               ` Andrew Morton
2008-07-30 23:41                 ` Stephen Rothwell
2008-07-30 23:44                   ` Greg KH
2008-08-07  1:08                     ` Stephen Rothwell
2008-08-07  3:40                       ` Greg KH
2008-08-07  6:10                         ` Stephen Rothwell
2008-07-30  1:05   ` linux-next: usb tree fix (Was: Re: linux-next: Tree for July 29) Stephen Rothwell
2008-07-30 19:38     ` Bartlomiej Zolnierkiewicz [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=200807302138.47972.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=gregkh@suse.de \
    --cc=haveblue@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox