From: Linus Torvalds <torvalds@linux-foundation.org>
To: mpe@ellerman.id.au
Cc: amodra@gmail.com, andrew.donnellan@au1.ibm.com,
aneesh.kumar@linux.ibm.com, anton@ozlabs.org, anton@samba.org,
aravinda@linux.vnet.ibm.com, Arnd Bergmann <arnd@arndb.de>,
b.zolnierkie@samsung.com, benh@kernel.crashing.org,
breno.leitao@gmail.com, christophe.leroy@c-s.fr,
clombard@linux.vnet.ibm.com, dan.carpenter@oracle.com,
dan.j.williams@intel.com, daniel.vetter@ffwll.ch, dja@axtens.net,
ego@linux.vnet.ibm.com, fbarrat@linux.vnet.ibm.com,
fthain@telegraphics.com.au, geert@linux-m68k.org,
geoff@infradead.org, hbathini@linux.ibm.com, joel@jms.id.au,
ldufour@linux.vnet.ibm.com, leitao@debian.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org, mahesh@linux.vnet.ibm.com,
mhairgrove@nvidia.com, mikey@neuling.org, msuchanek@suse.de,
mwb@linux.vnet.ibm.com, naveen.n.rao@linux.vnet.ibm.com,
nfont@linux.vnet.ibm.com, Nick Piggin <npiggin@gmail.com>,
oohall@gmail.com, paulus@ozlabs.org, pvorel@suse.cz,
rashmica.g@gmail.com, robh@kernel.org, sbobroff@linux.ibm.com,
sjitindarsingh@gmail.com, vaibhav@linux.ibm.com,
yamada.masahiro@socionext.com, yuehaibing@huawei.com,
zhongjiang@huawei.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-4.20-1 tag
Date: Fri, 26 Oct 2018 14:38:33 -0700 [thread overview]
Message-ID: <CAHk-=wj8hOhDQR61+R2w0YbOnXAmfvWWSvyN9pMsNU8MFF6wvw@mail.gmail.com> (raw)
In-Reply-To: <87ftwssg7m.fsf@concordia.ellerman.id.au>
On Fri, Oct 26, 2018 at 11:42 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> Please pull powerpc updates for 4.20:
Pulled,
Linus
prev parent reply other threads:[~2018-10-26 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 18:41 [GIT PULL] Please pull powerpc/linux.git powerpc-4.20-1 tag Michael Ellerman
2018-10-26 21:38 ` Linus Torvalds [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='CAHk-=wj8hOhDQR61+R2w0YbOnXAmfvWWSvyN9pMsNU8MFF6wvw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=amodra@gmail.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anton@ozlabs.org \
--cc=anton@samba.org \
--cc=aravinda@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=benh@kernel.crashing.org \
--cc=breno.leitao@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=clombard@linux.vnet.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dja@axtens.net \
--cc=ego@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=geoff@infradead.org \
--cc=hbathini@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=ldufour@linux.vnet.ibm.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mhairgrove@nvidia.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=mwb@linux.vnet.ibm.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=oohall@gmail.com \
--cc=paulus@ozlabs.org \
--cc=pvorel@suse.cz \
--cc=rashmica.g@gmail.com \
--cc=robh@kernel.org \
--cc=sbobroff@linux.ibm.com \
--cc=sjitindarsingh@gmail.com \
--cc=vaibhav@linux.ibm.com \
--cc=yamada.masahiro@socionext.com \
--cc=yuehaibing@huawei.com \
--cc=zhongjiang@huawei.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;
as well as URLs for NNTP newsgroup(s).