From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, "Tobin C. Harding" <me@tobin.cc>
Subject: Re: powerpc: fix sparse warning, include kernel header
Date: Tue, 21 Mar 2017 22:36:14 +1100 (AEDT) [thread overview]
Message-ID: <3vnW3f5czwz9s84@ozlabs.org> (raw)
In-Reply-To: <1488788731-2537-1-git-send-email-me@tobin.cc>
On Mon, 2017-03-06 at 08:25:31 UTC, "Tobin C. Harding" wrote:
> Spares emits two symbol not declared warnings. The two functions in
> question are declared already in a kernel header.
>
> Add include directive to include kernel header.
>
> Signed-off-by: Tobin C. Harding <me@tobin.cc>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/1fc439c81312cd27aed553964c0d9d
cheers
prev parent reply other threads:[~2017-03-21 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 8:25 [PATCH] powerpc: fix sparse warning, include kernel header Tobin C. Harding
2017-03-10 0:40 ` Daniel Axtens
2017-03-11 22:19 ` Tobin C. Harding
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=3vnW3f5czwz9s84@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).