All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Martin Mares <mj@ucw.cz>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] x86: loadflags cleanups
Date: Wed, 18 Feb 2015 23:06:50 +0100	[thread overview]
Message-ID: <20150218220650.GA28460@gmail.com> (raw)
In-Reply-To: <1422685925-6003-1-git-send-email-kuleshovmail@gmail.com>


* Alexander Kuleshov <kuleshovmail@gmail.com> wrote:

> There are a couple macros in the arch/x86/include/uapi/asm/bootparam.h
> for checking loadflags bits. Let's use it instead of shifting bits
> 
> Alexander Kuleshov (2):
>   x86: use already defined KEEP_SEGMENTS macro from bootparam.h
>   x86/boot: use already defined KEEP_SEGMENTS macro in head_{32,64}.S
> 
>  arch/x86/boot/compressed/head_32.S | 5 +++--
>  arch/x86/boot/compressed/head_64.S | 3 ++-
>  arch/x86/kernel/head_32.S          | 7 ++++---
>  3 files changed, 9 insertions(+), 6 deletions(-)

I think a single patch would be perfectly fine for a 
cleanup that does the same thing in three files.

Thanks,

	Ingo

  parent reply	other threads:[~2015-02-18 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31  6:32 [PATCH v2 0/2] x86: loadflags cleanups Alexander Kuleshov
2015-01-31  6:32 ` [PATCH v2 1/2] x86: use already defined KEEP_SEGMENTS macro from bootparam.h Alexander Kuleshov
2015-01-31  6:33 ` [PATCH v2 2/2] x86/boot: use already defined KEEP_SEGMENTS macro in head_{32,64}.S Alexander Kuleshov
2015-02-18 22:06 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-31  6:29 [PATCH v2 0/2] x86: loadflags cleanups Alexander Kuleshov

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=20150218220650.GA28460@gmail.com \
    --to=mingo@kernel.org \
    --cc=hpa@zytor.com \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mj@ucw.cz \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 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.