mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Masanari Iida <standby24x7@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] [linux-next] x86/smpboot: Remove duplicate inclusion of asm/reammode.h
Date: Mon, 13 Mar 2017 10:57:33 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1703131046370.3558@nanos> (raw)
In-Reply-To: <20170313093522.17391-1-standby24x7@gmail.com>

Masanari,

On Mon, 13 Mar 2017, Masanari Iida wrote:

> Subject : [PATCH] [linux-next] x86/smpboot: Remove duplicate inclusion of 
>          asm/reammode.h

The "linux-next" tag is pointless. The duplicate include is in Linus tree
as well, so this is not linux-next specific at all.

Please be more careful with your subject lines. reammode.h ????

> This patch remove duplicate asm/realmode.h in smpboot.c

Please read Documentation/process/submitting-patches.rst. Especially the
following paragraph:

  Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
  instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to
  do frotz", as if you are giving orders to the codebase to change its
  behaviour

"This patch" is really pointless. We already know that this is a patch,
otherwise you wouldn't have sent it with the "[PATCH]" prefix in the
subject line.

> Confirm successfully compile after remove the line.

That's obvious, isn't it? If the include is duplicate the removal won't
break anything.

> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> 
> # Please enter the commit message for your changes. Lines starting
> # with '#' will be kept; you may remove them yourself if you want to.
> # An empty message aborts the commit.
> # On branch smpboot-fix
> # Changes to be committed:
> #	modified:   arch/x86/kernel/smpboot.c
> #

Please adjust your workflow. This is not part of a changelog. It's the
comment section of the git-commit template which should not be part of your
patch submission at all.

Thanks,

	tglx

      reply	other threads:[~2017-03-13  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13  9:35 Masanari Iida
2017-03-13  9:57 ` Thomas Gleixner [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=alpine.DEB.2.20.1703131046370.3558@nanos \
    --to=tglx@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=standby24x7@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®