linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Borislav Petkov <bp@alien8.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andy Lutomirski <luto@kernel.org>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"elliott@hpe.com" <elliott@hpe.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-nvdimm@ml01.01.org" <linux-nvdimm@ml01.01.org>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v6 2/4] x86: Cleanup and add a new exception class
Date: Mon, 4 Jan 2016 14:23:21 -0800	[thread overview]
Message-ID: <CALCETrX9_itvAUdc1P4DA3GX9aHnkJYu1P4dH5ACzpYQvM7ccA@mail.gmail.com> (raw)
In-Reply-To: <20160104203212.GP22941@pd.tnic>

On Mon, Jan 4, 2016 at 12:32 PM, Borislav Petkov <bp@alien8.de> wrote:
> On Mon, Jan 04, 2016 at 05:00:04PM +0000, Luck, Tony wrote:
>> > So you're touching those again in patch 2. Why not add those defines to
>> > patch 1 directly and diminish the churn?
>>
>> To preserve authorship. Andy did patch 1 (the clever part). Patch 2 is just syntactic
>> sugar on top of it.
>
> That you can do in the way Ingo suggested.

I also personally don't care that much.  You're welcome to modify my patch.

If you modify it so much that it's mostly your patch, then change the
From: string and credit me.  If not, leave the author as me and make a
note in the log message.

--Andy

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-01-04 22:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04  1:02 [PATCH v6 0/4] Machine check recovery when kernel accesses poison Tony Luck
2015-12-30 17:59 ` [PATCH v6 1/4] x86: Clean up extable entry format (and free up a bit) Andy Lutomirski
2016-01-04  1:37   ` Tony Luck
2016-01-04  7:49     ` Ingo Molnar
2016-01-04 12:07   ` Borislav Petkov
2016-01-04 17:26     ` Tony Luck
2016-01-04 18:08       ` Andy Lutomirski
2016-01-04 18:59         ` Tony Luck
2016-01-04 19:05           ` Andy Lutomirski
2016-01-04 21:02         ` Borislav Petkov
2016-01-04 22:29           ` Andy Lutomirski
2016-01-04 23:02             ` Borislav Petkov
2016-01-04 23:04               ` Borislav Petkov
2016-01-04 23:25               ` Andy Lutomirski
2016-01-05 11:20                 ` Borislav Petkov
2016-01-04 23:11         ` Tony Luck
2015-12-30 18:56 ` [PATCH v6 2/4] x86: Cleanup and add a new exception class Tony Luck
2016-01-04 14:22   ` Borislav Petkov
2016-01-04 17:00     ` Luck, Tony
2016-01-04 20:32       ` Borislav Petkov
2016-01-04 22:23         ` Andy Lutomirski [this message]
2015-12-31 19:40 ` [PATCH v6 3/4] x86, mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries Tony Luck
2015-12-31 19:43 ` [PATCH v6 4/4] x86, mce: Add __mcsafe_copy() Tony Luck

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=CALCETrX9_itvAUdc1P4DA3GX9aHnkJYu1P4dH5ACzpYQvM7ccA@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=elliott@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=tony.luck@intel.com \
    --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 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).