From: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
To: Paul Bolle <pebolle@tiscali.nl>, Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH] mac802154: fix typo in header guard
Date: Thu, 19 Mar 2015 21:59:47 +0800 [thread overview]
Message-ID: <550AD653.4050306@m4x.org> (raw)
In-Reply-To: <1426772786.23529.4.camel@x220>
On 03/19/2015 09:46 PM, Paul Bolle wrote:
> On Thu, 2015-03-19 at 14:37 +0100, Alexander Aring wrote:
>> On Thu, Mar 19, 2015 at 09:23:40PM +0800, Nicolas Iooss wrote:
>>> Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
>>> Fixes: b6eea9ca354a ("mac802154: introduce driver-ops header")
>>
>> Acked-by: Alexander Aring <alex.aring@gmail.com>
>>
>> can you please queue this into bluetooth-next or even bluetooth?
>
> Is the Fixes: tag needed?
>
> mac802154.ko builds fine on my machine. There's also no error or warning
> included in the commit explanation. So it seems this is just a typo fix,
> not something that should be sent to stable too. Or did I miss something
> non-obvious?
No, you didn't miss anything. It is only a fix for a typo I found while
testing LLVMLinux (clang warns about such typos with -Wheader-guard).
I added a Fixes: tag because it is easier to remove it afterwards that
to search for a commit when adding it. I think this patch should not be
sent to stable@, and feel free to remove the tag if for you it means
"forward to stable@" (Documentation/SubmittingPatches is not clear about
whether a Fixes tag should be only used for real bugs or if it also
applies to compiler warnings).
Thanks for your quick replies.
Nicolas
next prev parent reply other threads:[~2015-03-19 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 13:23 [PATCH] mac802154: fix typo in header guard Nicolas Iooss
2015-03-19 13:37 ` Alexander Aring
2015-03-19 13:46 ` Paul Bolle
2015-03-19 13:58 ` Alexander Aring
2015-03-19 13:59 ` Nicolas Iooss [this message]
2015-03-19 14:33 ` Marcel Holtmann
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=550AD653.4050306@m4x.org \
--to=nicolas.iooss_linux@m4x.org \
--cc=alex.aring@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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.