From: Luca Ceresoli <luca@lucaceresoli.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Srikrishan Malik <srikrishanmalik@gmail.com>,
devel@driverdev.osuosl.org, Peng Tao <bergwolf@gmail.com>,
linux-kernel@vger.kernel.org, HPDD-discuss@ml01.01.org,
Jinshan Xiong <jinshan.xiong@intel.com>
Subject: Re: [PATCH 2/2] staging: lustre: declare internal symbols as static
Date: Sun, 18 Jan 2015 14:49:40 +0100 [thread overview]
Message-ID: <54BBB9F4.1010404@lucaceresoli.net> (raw)
In-Reply-To: <20150118000214.GA25744@kroah.com>
Dear Greg,
Greg Kroah-Hartman wrote:
> On Tue, Jan 13, 2015 at 11:33:03PM +0100, Luca Ceresoli wrote:
>> Fixes dozens of sparse warnings like:
>> warning: symbol 'cfs_tracefile_sem' was not declared. Should it be static?
>>
>> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
>> Cc: Peng Tao <bergwolf@gmail.com>
>> Cc: Jinshan Xiong <jinshan.xiong@intel.com>
>> Cc: Srikrishan Malik <srikrishanmalik@gmail.com>
>> Cc: HPDD-discuss@lists.01.org
>> Cc: devel@driverdev.osuosl.org
>> Cc: linux-kernel@vger.kernel.org
>
> This patch fails to apply to my staging-next branch, sorry :(
Some of my fixes were done by somebody else in the meantime.
Several people are sending small fixes for staging every day.
So, to reduce the probability of further conflicts, I'm resending
this patch as a set of smaller ones.
--
Luca
prev parent reply other threads:[~2015-01-18 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 22:33 [PATCH 1/2] staging/lustre: remove unused function Luca Ceresoli
2015-01-13 22:33 ` [PATCH 2/2] staging: lustre: declare internal symbols as static Luca Ceresoli
2015-01-18 0:02 ` Greg Kroah-Hartman
2015-01-18 13:49 ` Luca Ceresoli [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=54BBB9F4.1010404@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jinshan.xiong@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=srikrishanmalik@gmail.com \
/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
all inboxes | Powered by JetHome®