From: Kalle Valo <kvalo@kernel.org>
To: Sven Eckelmann <se@simonwunderlich.de>
Cc: ih@simonwunderlich.de, sw@simonwunderlich.de,
johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
mathias.kretschmer@fit.fraunhofer.de
Subject: Re: [PATCH v2 2/2] wifi: ath9k: Reset chip on potential deaf state
Date: Thu, 07 Nov 2024 10:03:17 +0200 [thread overview]
Message-ID: <87fro3xygq.fsf@kernel.org> (raw)
In-Reply-To: <865447434.0ifERbkFSE@ripper> (Sven Eckelmann's message of "Wed, 06 Nov 2024 11:05:57 +0100")
Sven Eckelmann <se@simonwunderlich.de> writes:
> On Wednesday, 6 November 2024 10:04:39 CET Issam Hamdi wrote:
> [...]
>> This patch originally developed by "Simon Wunderlich <simon.wunderlich@open-mesh.com>"
>> and "Sven Eckelmann <sven.eckelmann@open-mesh.com>"
>
> Am I the only person which finds this style of adding information about "Co-
> authors" weird?
No, you are not. I also find it weird.
> [...]
>> Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
>> Signed-off-by: Sven Eckelmann <se@simonwunderlich.de>
>> Signed-off-by: Issam Hamdi <ih@simonwunderlich.de>
>> ---
>> v2: change the "Co-developed-by" to "Signed-off-by", remove the dependency
>
> I think Kalle meant that "Co-developed-by" should be followed by a
> "Signed-off-by" - not that "Co-developed-by" should be removed.
Correct, to my understanding having both c-d-b and s-o-b is the
preferred format.
>> on CONFIG_ATH9K_DEBUGFS and add more information in the commit description
>
> And please don't reply to the old thread when sending a new patchset - this
> becomes really unreadable after a while. You can simply use the method which
> b4 uses and just reference the old thread in your mail. Something like:
>
> Changes in v2:
> - change the "Co-developed-by" to "Signed-off-by"
> - remove the dependency on CONFIG_ATH9K_DEBUGFS
> - add more information in the commit description
> - Link to v1: https://lore.kernel.org/r/20241104171627.3789199-1-ih@simonwunderlich.de
Yes, this style is very much recommended. Having links to older versions
helps reviewers.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-11-07 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 17:16 [PATCH 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Issam Hamdi
2024-11-04 17:16 ` [PATCH 2/2] wifi: ath9k: Reset chip on potential deaf state Issam Hamdi
2024-11-05 10:53 ` Kalle Valo
2024-11-05 13:02 ` Toke Høiland-Jørgensen
2024-11-05 13:30 ` Simon Wunderlich
2024-11-05 15:10 ` Toke Høiland-Jørgensen
2024-11-06 10:05 ` Hamdi Issam
2024-11-05 13:34 ` Simon Wunderlich
2024-11-05 10:49 ` [PATCH 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Kalle Valo
2024-11-05 12:31 ` Toke Høiland-Jørgensen
2024-11-06 9:04 ` [PATCH v2 " Issam Hamdi
2024-11-06 9:04 ` [PATCH v2 2/2] wifi: ath9k: Reset chip on potential deaf state Issam Hamdi
2024-11-06 10:05 ` Sven Eckelmann
2024-11-06 12:41 ` Toke Høiland-Jørgensen
2024-11-07 8:03 ` Kalle Valo [this message]
2024-11-06 10:06 ` [PATCH v2 1/2] wifi: ath9k: work around AR_CFG 0xdeadbeef chip hang Sven Eckelmann
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=87fro3xygq.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ih@simonwunderlich.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fit.fraunhofer.de \
--cc=se@simonwunderlich.de \
--cc=sw@simonwunderlich.de \
/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.