From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: tcharding <me@tobin.cc>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, "Tobin C. Harding" <me@tobin.cc>
Subject: Re: [RESEND] powerpc/pseries: move struct hcall_stats to c file
Date: Tue, 21 Mar 2017 22:36:16 +1100 (AEDT) [thread overview]
Message-ID: <3vnW3h4lJPz9s8B@ozlabs.org> (raw)
In-Reply-To: <1488879162-20596-1-git-send-email-me@tobin.cc>
On Tue, 2017-03-07 at 09:32:42 UTC, tcharding wrote:
> struct hcall_stats is only used in hvCall_inst.c.
>
> Move struct hcall_stats to hvCall_inst.c
>
> Signed-off-by: Tobin C. Harding <me@tobin.cc>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/017614a5d6c09ec9e0dc3fd46a5018
cheers
prev parent reply other threads:[~2017-03-21 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 9:32 [RESEND PATCH] powerpc/pseries: move struct hcall_stats to c file Tobin C. Harding
2017-03-08 0:37 ` Michael Ellerman
2017-03-21 11:36 ` 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=3vnW3h4lJPz9s8B@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=me@tobin.cc \
--cc=paulus@samba.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).