From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Daniel Axtens <dja@axtens.net>, linuxppc-dev@ozlabs.org
Cc: mikey@neuling.org, Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH 1/2] powerpc: sparse: static-ify some things
Date: Fri, 08 Jan 2016 17:30:30 +1100 [thread overview]
Message-ID: <87lh80furd.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1452041151-2387-1-git-send-email-dja@axtens.net>
Daniel Axtens <dja@axtens.net> writes:
> As sparse suggests, these should be made static.
>
> Signed-off-by: Daniel Axtens <dja@axtens.net>
Reviewed-by: Stewart Smith <stewart@linux.vnet.ibm.com>
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2016-01-10 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 0:45 [PATCH 1/2] powerpc: sparse: static-ify some things Daniel Axtens
2016-01-06 0:45 ` [PATCH 2/2] powerpc: sparse: Include headers for __weak symbols Daniel Axtens
2016-01-06 2:08 ` [PATCH 1/2] powerpc: sparse: static-ify some things Andrew Donnellan
2016-01-08 6:30 ` Stewart Smith [this message]
2016-04-13 13:33 ` [1/2] " Michael Ellerman
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=87lh80furd.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=dja@axtens.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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).