From: Boaz Harrosh <bharrosh@panasas.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: LKML <linux-kernel@vger.kernel.org>, <osd-dev@open-osd.org>,
Benny Halevy <bhalevy@tonian.com>,
Andrew Morton <akpm@linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] exofs: fix sparse non-ANSI function warning
Date: Tue, 12 Jun 2012 09:21:46 +0300 [thread overview]
Message-ID: <4FD6DFFA.2050802@panasas.com> (raw)
In-Reply-To: <4FD6DC7A.9000709@panasas.com>
On 06/12/2012 09:06 AM, Boaz Harrosh wrote:
> On 06/12/2012 02:46 AM, Randy Dunlap wrote:
>
>> From: Randy Dunlap <rdunlap@xenotime.net>
>>
>> Fix sparse non-ANSI function warning:
>>
>> fs/exofs/sys.c:112:28: warning: non-ANSI function declaration of function 'exofs_sysfs_dbg_print'
>>
>
>
> Thanks, will push for 3.6 merge window. Might take me
> a few days to push to linux-next
>
Linus already pushed this for -rc3, cool less work for me ;-)
Thanks guys
Boaz
> Boaz
>
prev parent reply other threads:[~2012-06-12 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 23:46 [PATCH] exofs: fix sparse non-ANSI function warning Randy Dunlap
2012-06-12 6:06 ` Boaz Harrosh
2012-06-12 6:21 ` Boaz Harrosh [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=4FD6DFFA.2050802@panasas.com \
--to=bharrosh@panasas.com \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@tonian.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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