From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Stewart Smith <stewart@linux•ibm.com>, linuxppc-dev@lists•ozlabs.org
Cc: sbobroff@linux•ibm.com, paulus@samba•org, oohall@gmail•com,
Stewart Smith <stewart@linux•ibm.com>
Subject: Re: [TRIVIAL] [PATCH] powerpc/powernv-eeh: Consisely desribe what this file does
Date: Mon, 8 Jul 2019 11:19:33 +1000 (AEST) [thread overview]
Message-ID: <45hnft2p3Fz9sP7@ozlabs.org> (raw)
In-Reply-To: <20190528032925.8836-1-stewart@linux.ibm.com>
On Tue, 2019-05-28 at 03:29:25 UTC, Stewart Smith wrote:
> If the previous comment made sense, continue debugging or call your
> doctor immediately.
>
> Signed-off-by: Stewart Smith <stewart@linux•ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/41732bdc9ccd26829cf647711c4b93384e03e529
cheers
prev parent reply other threads:[~2019-07-08 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 3:29 [TRIVIAL] [PATCH] powerpc/powernv-eeh: Consisely desribe what this file does Stewart Smith
2019-05-28 4:03 ` Oliver
2019-05-28 4:43 ` Stewart Smith
2019-05-28 4:20 ` Russell Currey
2019-07-08 1:19 ` Michael Ellerman [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=45hnft2p3Fz9sP7@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=oohall@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=sbobroff@linux$(echo .)ibm.com \
--cc=stewart@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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