Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Eric DeVolder <eric.devolder@oracle.com>
Cc: andrew.cooper3@citrix.com, daniel.kiper@oracle.com,
	kexec@lists.infradead.org
Subject: Re: [PATCH 0/2] Simple cleanups
Date: Tue, 31 Jan 2017 12:24:41 +0100	[thread overview]
Message-ID: <20170131112441.GA15624@verge.net.au> (raw)
In-Reply-To: <1485800065-1573-1-git-send-email-eric.devolder@oracle.com>

On Mon, Jan 30, 2017 at 12:14:23PM -0600, Eric DeVolder wrote:
> Trivial cleanups
> 
> No functional changes

Thanks, applied.

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

      parent reply	other threads:[~2017-01-31 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 18:14 [PATCH 0/2] Simple cleanups Eric DeVolder
2017-01-30 18:14 ` [PATCH 1/2] purgatory: Add purgatory.map and purgatory.ro.sym to clean recipe Eric DeVolder
2017-01-30 18:14 ` [PATCH 2/2] kexec: Remove redundant space from help message Eric DeVolder
2017-01-31 11:24 ` Simon Horman [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=20170131112441.GA15624@verge.net.au \
    --to=horms@verge.net.au \
    --cc=andrew.cooper3@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=eric.devolder@oracle.com \
    --cc=kexec@lists.infradead.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