All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Taras Kondratiuk <taras.kondratiuk@linaro.org>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	WANG Chao <chaowang@redhat.com>, Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH] vmcore-dmesg: Handle struct log to struct printk_log renaming
Date: Wed, 28 May 2014 08:45:53 +0900	[thread overview]
Message-ID: <20140527234553.GC7374@verge.net.au> (raw)
In-Reply-To: <20140527131342.GD10994@redhat.com>

On Tue, May 27, 2014 at 09:13:42AM -0400, Vivek Goyal wrote:
> On Mon, May 26, 2014 at 03:54:22PM +0900, Simon Horman wrote:
> > On Thu, May 22, 2014 at 10:43:14AM -0400, Vivek Goyal wrote:
> > > vmcore-dmesg has been failing for me for quite some time as struct log
> > > was renamed to struct printk_log.
> > > 
> > > 62e32ac printk: rename struct log to struct printk_log
> > > 
> > > This patch has been sitting in mailing list for quite some time. It
> > > is time to repost the patch.
> > > 
> > > I took original patch of Lubomir and modified a bit to take care of
> > > concern of hardcoded string length.
> > > 
> > > Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
> > > Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
> > > ---
> > > 
> > > Changes for v2:
> > >   * Clarified printk_log vs. log in some comments.
> > 
> > Thanks, applied.
> 
> Thanks Simon. "git pull" did not result in anything. Have you pushed it
> out yet?

Sorry about that, I have pushed it now.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-05-27 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 14:43 [PATCH] vmcore-dmesg: Handle struct log to struct printk_log renaming Vivek Goyal
2014-05-26  6:54 ` Simon Horman
2014-05-27 13:13   ` Vivek Goyal
2014-05-27 23:45     ` Simon Horman [this message]
2014-05-28 12:27       ` Vivek Goyal

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=20140527234553.GC7374@verge.net.au \
    --to=horms@verge.net.au \
    --cc=chaowang@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=lkundrak@v3.sk \
    --cc=taras.kondratiuk@linaro.org \
    --cc=vgoyal@redhat.com \
    /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.