From: Hugh Dickins <hugh@veritas•com>
To: Greg KH <gregkh@suse•de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Bernhard Walle <bwalle@suse•de>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Dave Hansen <haveblue@us•ibm.com>
Subject: Re: linux-next: Tree for July 29
Date: Tue, 29 Jul 2008 21:49:24 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0807292145220.28604@blonde.site> (raw)
In-Reply-To: <20080729181639.GA21311@suse.de>
On Tue, 29 Jul 2008, Greg KH wrote:
> On Tue, Jul 29, 2008 at 06:25:14PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Tuesday 29 July 2008, Stephen Rothwell wrote:
> > >
> > > Changes since next-20080728:
> >
> > 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?
>
> What is the problem with this patch that has caused it to suddenly
> keeping the boot from working? Is the code in the patch warning you of
> objects that are not properly being initialized?
>
> I'll be glad to fix this if possible.
Isn't this the opposite end of the same problem for which Bernhard
has been repeatedly trying to find a taker for his patch:
http://article.gmane.org/gmane.linux.kernel.kexec/1882
Hugh
next prev parent reply other threads:[~2008-07-29 20:49 UTC|newest]
Thread overview: 26+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-07-29 7:36 linux-next: Tree for July 29 Stephen Rothwell
2010-07-29 4:32 Stephen Rothwell
2011-07-29 7:38 Stephen Rothwell
2011-07-30 11:38 ` Sedat Dilek
2011-07-30 16:08 ` Arnaud Lacombe
2011-07-30 16:16 ` Sedat Dilek
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=Pine.LNX.4.64.0807292145220.28604@blonde.site \
--to=hugh@veritas$(echo .)com \
--cc=bwalle@suse$(echo .)de \
--cc=bzolnier@gmail$(echo .)com \
--cc=gregkh@suse$(echo .)de \
--cc=haveblue@us$(echo .)ibm.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