From: Ingo Molnar <mingo@kernel.org>
To: Tony Luck <tony.luck@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Dan Williams <dan.j.williams@intel.com>, Robert <elliott@hpe.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-nvdimm <linux-nvdimm@ml01.01.org>, X86-ML <x86@kernel.org>
Subject: Re: [PATCH v6 1/4] x86: Clean up extable entry format (and free up a bit)
Date: Mon, 4 Jan 2016 08:49:03 +0100 [thread overview]
Message-ID: <20160104074903.GA4227@gmail.com> (raw)
In-Reply-To: <CA+8MBbKuOHHwYeFHFePAts=DE=iR4aQUcfjDzGEg7u5ihTDmLg@mail.gmail.com>
* Tony Luck <tony.luck@gmail.com> wrote:
> On Wed, Dec 30, 2015 at 9:59 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> > This adds two bits of fixup class information to a fixup entry,
> > generalizing the uaccess_err hack currently in place.
> >
> > Forward-ported-from-3.9-by: Tony Luck <tony.luck@intel.com>
> > Signed-off-by: Andy Lutomirski <luto@amacapital.net>
>
> Crivens! I messed up when "git cherrypick"ing this and "git
> format-patch"ing it.
>
> I didn't mean to forge Andy's From line when sending this out (just to have a
> From: line to give him credit.for the patch).
>
> Big OOPs ... this is "From:" me ... not Andy!
But in any case it's missing your SOB line.
If Andy is still the primary author (much of his original patch survived, you
resolved conflicts or minor changes) then you can send this as:
From: Tony Luck <tony.luck@intel.com>
Subject: [PATCH v6 1/4] x86: Clean up extable entry format (and free up a bit)
From: Andy Lutomirski <luto@amacapital.net>
... changelog ...
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
[ Forward ported from a v3.9 version. ]
Signed-off-by: Tony Luck <tony.luck@intel.com
This carries all the information, has a proper SOB chain, and preserves
authorship. Also, it's clear from the tags that you made material changes, so any
resulting breakage is yours (and mine), not Andy's! ;-)
If the changes to the patch are major, so that your new work is larger than Andy's
original work, you can still credit him via a non-standard tag, like:
From: Tony Luck <tony.luck@intel.com>
Subject: [PATCH v6 1/4] x86: Clean up extable entry format (and free up a bit)
This patch is based on Andy Lutomirski's patch sent against v3.9:
... changelog ...
Originally-from: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Tony Luck <tony.luck@intel.com
Thanks,
Ingo
--
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>
next prev parent reply other threads:[~2016-01-04 7:49 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 [this message]
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
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=20160104074903.GA4227@gmail.com \
--to=mingo@kernel.org \
--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@amacapital.net \
--cc=luto@kernel.org \
--cc=tony.luck@gmail.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).