All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hong Xu <hong@topbug.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k and ath9k_htc: rename variable "led_blink"
Date: Sat, 24 Jan 2015 03:10:23 -0800	[thread overview]
Message-ID: <87twzgmo2o.fsf@home.hong.me> (raw)
In-Reply-To: <CA+icZUVq-bhryv=Aj7JuCzFU6kTQEh+jiwBR_bnJzNnjJ2Kg-A@mail.gmail.com>


Sedat Dilek <sedat.dilek@gmail.com> writes:

> On Sat, Jan 24, 2015 at 11:23 AM, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Hong Xu <hong@topbug.net> writes:
>>
>>> ath9k and ath9k_htc use the variable name "led_blink" to indicate
>>> whether the module parameter "blink" is on. This name is easy to
>>> conflict with other variables, thus they are renamed.
>>
>> Please state clearly that this fixes a compiler error found by kbuild.
>> Also it's very much recommended to add the actual compiler error to the
>> commit log:
>>
>> drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0x47c): multiple definition of `led_blink'
>> drivers/net/wireless/ath/ath9k/ath9k.o:(.bss+0x20): first defined here
>>
>
> Some more things...
>
> If you post a vN (referring to your v3) of a patch, please add a
> history of changes.
>
> 2nd, use the Fixes tag [2] in this case with a reference to the
> culprit commit [1].
>
> Fixes: 3a939a671225 ("ath9k_htc: Add a module parameter to disable blink")
>
> Last but not least, honour credits like Reported-by/Tested-by (plus
> some infos like broken in Linux-next $VERSION).
>
Thanks for your comments, I should have been more careful with the
guideline. I guess we shouldn't credit kbuild for reporting in this case?

Hong
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20150124/8ac921fd/attachment.pgp 

WARNING: multiple messages have this Message-ID (diff)
From: Hong Xu <hong@topbug.net>
To: sedat.dilek@gmail.com
Cc: Kalle Valo <kvalo@codeaurora.org>,
	wireless <linux-wireless@vger.kernel.org>,
	ath9k-devel@lists.ath9k.org
Subject: Re: [PATCH] ath9k and ath9k_htc: rename variable "led_blink"
Date: Sat, 24 Jan 2015 03:10:23 -0800	[thread overview]
Message-ID: <87twzgmo2o.fsf@home.hong.me> (raw)
In-Reply-To: <CA+icZUVq-bhryv=Aj7JuCzFU6kTQEh+jiwBR_bnJzNnjJ2Kg-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]


Sedat Dilek <sedat.dilek@gmail.com> writes:

> On Sat, Jan 24, 2015 at 11:23 AM, Kalle Valo <kvalo@codeaurora.org> wrote:
>> Hong Xu <hong@topbug.net> writes:
>>
>>> ath9k and ath9k_htc use the variable name "led_blink" to indicate
>>> whether the module parameter "blink" is on. This name is easy to
>>> conflict with other variables, thus they are renamed.
>>
>> Please state clearly that this fixes a compiler error found by kbuild.
>> Also it's very much recommended to add the actual compiler error to the
>> commit log:
>>
>> drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0x47c): multiple definition of `led_blink'
>> drivers/net/wireless/ath/ath9k/ath9k.o:(.bss+0x20): first defined here
>>
>
> Some more things...
>
> If you post a vN (referring to your v3) of a patch, please add a
> history of changes.
>
> 2nd, use the Fixes tag [2] in this case with a reference to the
> culprit commit [1].
>
> Fixes: 3a939a671225 ("ath9k_htc: Add a module parameter to disable blink")
>
> Last but not least, honour credits like Reported-by/Tested-by (plus
> some infos like broken in Linux-next $VERSION).
>
Thanks for your comments, I should have been more careful with the
guideline. I guess we shouldn't credit kbuild for reporting in this case?

Hong

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  parent reply	other threads:[~2015-01-24 11:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24 10:19 [ath9k-devel] [PATCH] ath9k and ath9k_htc: rename variable "led_blink" Hong Xu
2015-01-24 10:19 ` Hong Xu
2015-01-24 10:23 ` [ath9k-devel] " Kalle Valo
2015-01-24 10:23   ` Kalle Valo
2015-01-24 10:33   ` [ath9k-devel] " Sedat Dilek
2015-01-24 10:33     ` Sedat Dilek
2015-01-24 10:38     ` [ath9k-devel] " Oleksij Rempel
2015-01-24 10:38       ` Oleksij Rempel
2015-01-24 10:44       ` [ath9k-devel] " Sedat Dilek
2015-01-24 10:44         ` Sedat Dilek
2015-01-24 10:39     ` Kalle Valo
2015-01-24 10:50       ` Sedat Dilek
2015-01-24 11:07         ` Sedat Dilek
2015-01-24 11:10     ` Hong Xu [this message]
2015-01-24 11:10       ` Hong Xu
2015-01-24 11:22       ` [ath9k-devel] " Sedat Dilek
2015-01-24 11:22         ` Sedat Dilek

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=87twzgmo2o.fsf@home.hong.me \
    --to=hong@topbug.net \
    --cc=ath9k-devel@lists.ath9k.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 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.