From: Anton Vorontsov <anton.vorontsov@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Kay Sievers <kay@vrfy.org>,
Jason Wessel <jason.wessel@windriver.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net, stable@vger.kernel.org
Subject: Re: [PATCH for-3.5 1/4] kdb: Revive dmesg command
Date: Mon, 23 Jul 2012 16:38:20 -0700 [thread overview]
Message-ID: <20120723233819.GA6711@lizard> (raw)
In-Reply-To: <20120723161927.9af62e29.akpm@linux-foundation.org>
On Mon, Jul 23, 2012 at 04:19:27PM -0700, Andrew Morton wrote:
> > dmesg command appears to be broken after the printk rework. The old logic
> > in kdb code makes no sense in terms of current printk/logging storage
> > format, and KDB simply hangs forever.
> >
> > This patch revives the command by switching to kmsg_dumper iterator.
> >
> > The code is now much more simpler and shorter.
> >
> > Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
>
> This one should me merged into 3.5.1 methinks. Note that it has been
> merged into mainline without a -stable tag.
Thanks to Linus, it made it into v3.5 release, so I believe there is
no need for -stable.
Cheers,
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2012-07-23 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 0:25 [PATCH 0/4] KDB: Fix dmesg command Anton Vorontsov
2012-07-21 0:27 ` [PATCH for-3.5 1/4] kdb: Revive " Anton Vorontsov
2012-07-23 23:19 ` Andrew Morton
2012-07-23 23:38 ` Anton Vorontsov [this message]
2012-07-21 0:27 ` [PATCH 2/4] printk: Remove kdb_syslog_data Anton Vorontsov
2012-07-21 0:28 ` [PATCH 3/4] printk: Implement some unlocked kmsg_dump functions Anton Vorontsov
2012-07-21 0:28 ` [PATCH 4/4] kdb: Switch to nolock variants of " Anton Vorontsov
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=20120723233819.GA6711@lizard \
--to=anton.vorontsov@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.wessel@windriver.com \
--cc=kay@vrfy.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).