From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Anton Blanchard <anton@linux.ibm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ulrich Weigand <uweigand@de.ibm.com>,
paulmck@kernel.org, jejb@linux.ibm.com,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: provide IBM contacts for embargoed hardware
Date: Thu, 26 Mar 2020 15:26:01 +0100 [thread overview]
Message-ID: <20200326142601.GB1332382@kroah.com> (raw)
In-Reply-To: <82f6ea14-cb56-4546-20e1-7919dcd0d668@de.ibm.com>
On Thu, Mar 26, 2020 at 03:14:24PM +0100, Christian Borntraeger wrote:
>
>
> On 26.03.20 15:07, Greg Kroah-Hartman wrote:
> > On Thu, Mar 26, 2020 at 09:04:01PM +1100, Anton Blanchard wrote:
> >> Hi Greg,
> >>
> >>> On Thu, Mar 26, 2020 at 10:38:31AM +0100, Christian Borntraeger wrote:
> >>>> Provide IBM contact for embargoed hardware issues. As POWER and Z
> >>>> are different teams with different designs it makes sense to have
> >>>> separate persons for the first contact.
> >>>>
> >>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> >>>> Cc: Anton Blanchard <anton@linux.ibm.com>
> >>>> ---
> >>>> Documentation/process/embargoed-hardware-issues.rst | 3 ++-
> >>>> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/Documentation/process/embargoed-hardware-issues.rst
> >>>> b/Documentation/process/embargoed-hardware-issues.rst index
> >>>> a19d084f9b2c..43cdc67e4f8e 100644 ---
> >>>> a/Documentation/process/embargoed-hardware-issues.rst +++
> >>>> b/Documentation/process/embargoed-hardware-issues.rst @@ -246,7
> >>>> +246,8 @@ an involved disclosed party. The current ambassadors
> >>>> list: =============
> >>>> ======================================================== ARM
> >>>> Grant Likely <grant.likely@arm.com> AMD Tom
> >>>> Lendacky <tom.lendacky@amd.com>
> >>>> - IBM
> >>>> + IBM Z Christian Borntraeger <borntraeger@de.ibm.com>
> >>>> + IBM Power Anton Blanchard <anton@linux.ibm.com>
> >>>
> >>> Can I get an ack from Anton that he really agrees with this? :)
> >>
> >> Sure :)
> >>
> >> Acked-by: Anton Blanchard <anton@linux.ibm.com>
> >
> > Sucker :)
> >
> > thanks, I'll go queue this up now, and I will fix the checkpatch
> > warning...
>
> Huh?
>
> scripts/checkpatch.pl --strict rrr/0001-Documentation-provide-IBM-contacts-for-embargoed-har.patch
> total: 0 errors, 0 warnings, 0 checks, 9 lines checked
>
> rrr/0001-Documentation-provide-IBM-contacts-for-embargoed-har.patch has no obvious style problems and is ready for submission.
>
>
> Anything that I missed?
>
Hm, no, the original was fine, but if you look above there's trailing
whitespace after Anton's name on the line and I assumed it was in the
original. Must have gotten added somewhere along the reply-to chain.
sorry for the noise.
greg k-h
prev parent reply other threads:[~2020-03-26 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 9:38 Christian Borntraeger
2020-03-26 9:42 ` Greg Kroah-Hartman
2020-03-26 10:04 ` Anton Blanchard
2020-03-26 14:07 ` Greg Kroah-Hartman
2020-03-26 14:14 ` Christian Borntraeger
2020-03-26 14:26 ` Greg Kroah-Hartman [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=20200326142601.GB1332382@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anton@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=corbet@lwn.net \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
--cc=uweigand@de.ibm.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®