From: Andi Shyti <andi.shyti@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: lustre: Fix non-ANSI sparse warnings
Date: Sat, 27 Jul 2013 21:32:24 +0000 [thread overview]
Message-ID: <20130727213224.GB29842@jack.whiskey> (raw)
In-Reply-To: <1374950412-15973-1-git-send-email-emilgoode@gmail.com>
> I ususally put the warnings in the change log but when it's a long list
> I prefer leaving them out. If you would like the full list I can resend.
> Perhaps I should change the commit message to:
> This patch fixes a lot of non-ANSI sparse warnings by adding void to
> parameterless functions.
that's better
Andi
prev parent reply other threads:[~2013-07-27 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 18:40 [PATCH 1/2] staging: lustre: Fix non-ANSI sparse warnings Emil Goode
2013-07-27 19:20 ` Andi Shyti
2013-07-27 19:53 ` Emil Goode
2013-07-27 21:32 ` Andi Shyti [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=20130727213224.GB29842@jack.whiskey \
--to=andi.shyti@gmail.com \
--cc=kernel-janitors@vger.kernel.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