From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Kay Sievers <kay@vrfy.org>
Subject: Re: linux-next: Tree for Jun 18 (kmsg problems)
Date: Tue, 19 Jun 2012 08:37:20 +1000 [thread overview]
Message-ID: <20120619083720.996b2d743cff619a58e1de97@canb.auug.org.au> (raw)
In-Reply-To: <20120618221535.GA13037@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
Hi Greg,
On Mon, 18 Jun 2012 15:15:35 -0700 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> > Caused by commit e2ae715d66bf ("kmsg - kmsg_dump() use iterator to
> > receive log buffer content") from the driver-core.current tree.
>
> I'm building my tree right now, and I can't seem to hit this.
You need CONFIG_PRINTK turned off ...
> > This was reported a few days ago. Why is it not fixed yet?
>
> It was reported Friday evening, on a holiday weekend for some of us, we
> are trying the best we can :)
Ah ha, another of those pesky holiday things :-)
> > Especially since it is in a branch that is supposedly "bug fixes"?
>
> It fixes up a reported problem, and we had 3 people test it and said it
> resolved the issue for them, no build problems reported.
My usual mantra is that if your patch is modifying code that clearly
depends on a CONFIG option, you must test with that option both on and
off. I see build problems in linux-next all the time where this has not
been done. :-(
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-18 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 6:53 linux-next: Tree for Jun 18 Stephen Rothwell
2012-06-18 17:13 ` linux-next: Tree for Jun 18 (kmsg problems) Randy Dunlap
2012-06-18 22:01 ` Stephen Rothwell
2012-06-18 22:15 ` Greg Kroah-Hartman
2012-06-18 22:17 ` Kay Sievers
2012-06-18 22:32 ` Kay Sievers
2012-06-19 0:33 ` Randy Dunlap
2012-06-18 22:35 ` Greg Kroah-Hartman
2012-06-18 22:19 ` Randy Dunlap
2012-06-18 22:37 ` Stephen Rothwell [this message]
2012-06-18 22:45 ` Greg Kroah-Hartman
2012-06-18 17:31 ` linux-next: Tree for Jun 18 (netfilter nfconntrack) Randy Dunlap
2012-06-19 3:19 ` Pablo Neira Ayuso
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=20120619083720.996b2d743cff619a58e1de97@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.