From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Subject: Re: [1/3] powerpc/pseries: Move vio.c into platforms pseries
Date: Tue, 22 Nov 2016 11:34:15 +1100 (AEDT)	[thread overview]
Message-ID: <3tN60l6Fhqz9s5w@ozlabs.org> (raw)
In-Reply-To: <1479181664-6699-1-git-send-email-mpe@ellerman.id.au>
On Tue, 2016-11-15 at 03:47:42 UTC, Michael Ellerman wrote:
> vio.c is pseries only code, so move it in there.
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Series applied to powerpc next.
https://git.kernel.org/powerpc/c/139ac5afe30bcad3e0a8064a2fac60
cheers
     prev parent reply	other threads:[~2016-11-22  0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  3:47 [PATCH 1/3] powerpc/pseries: Move vio.c into platforms pseries Michael Ellerman
2016-11-15  3:47 ` [PATCH 2/3] powerpc/pseries: Move ibmebus.c " Michael Ellerman
2016-11-15  3:47 ` [PATCH 3/3] powerpc/pseries: Disable IBMEBUS on little endian builds Michael Ellerman
2016-11-22  0:34 ` 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=3tN60l6Fhqz9s5w@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).