From: Greg KH <gregkh@linuxfoundation.org>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
arve@android.com, riandrews@android.com,
devel@driverdev.osuosl.org, xie.baoyou@zte.com.cn,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] staging/android: mark sync_timeline_create() static
Date: Mon, 12 Sep 2016 11:45:45 +0200 [thread overview]
Message-ID: <20160912094545.GA20335@kroah.com> (raw)
In-Reply-To: <CA+DQWkxtL60FcGiV+ucmMPuviLFtjBrnbQYDU14ypzNgg_TriQ@mail.gmail.com>
On Mon, Sep 05, 2016 at 08:40:25AM +0800, Baoyou Xie wrote:
>
>
> On 4 September 2016 at 23:41, Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> wrote:
>
> On Sat, Sep 03, 2016 at 02:34:13PM +0800, Baoyou Xie wrote:
> > We get 1 warning when building kernel with W=1:
> > drivers/staging/android/sw_sync.c:56:23: warning: no previous prototype
> for 'sync_timeline_create' [-Wmissing-prototypes]
> >
> > In fact, this function is only used in the file in which it is
> > declared and don't need a declaration, but can be made static.
> > so this patch marks this function with 'static'.
> >
> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> > ---
> > drivers/staging/android/sw_sync.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> which tree are you using?
>
>
> I using master tree with 4.8-rc1
That's a quick way to ensure that your patches will not apply, as that
tree does not contain any of the patches submitted since then.
Please always work against linux-next or my staging-next tree for
staging patches.
thanks,
greg k-h
prev parent reply other threads:[~2016-09-12 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 6:34 [PATCH] staging/android: mark sync_timeline_create() static Baoyou Xie
2016-09-04 15:41 ` Sudip Mukherjee
[not found] ` <CA+DQWkxtL60FcGiV+ucmMPuviLFtjBrnbQYDU14ypzNgg_TriQ@mail.gmail.com>
2016-09-12 9:45 ` Greg KH [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=20160912094545.GA20335@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=baoyou.xie@linaro.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=xie.baoyou@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.