From: Johannes Berg <johannes@sipsolutions.net>
To: yiboz@codeaurora.org
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/4] mac80211: fix issue in loop scenario
Date: Wed, 18 Dec 2019 11:18:51 +0100 [thread overview]
Message-ID: <c126d2ff0866faf9ac50b12920f0497b03b031f7.camel@sipsolutions.net> (raw)
In-Reply-To: <6f092bd44cfc581a219bd0f0506cc636@codeaurora.org>
On Wed, 2019-12-18 at 18:12 +0800, yiboz@codeaurora.org wrote:
>
> Yes, this is a fix to the first patch. Actually, the rest of two patches
> are also serve the same. So, are you suggesting to merge them to the
> first patch?
Yes.
> Previouly, I had added Toke's signature in this patch but Toke advised
> to delete it. I feel a little bit confused about how to handle it.
> Appreciate any detail guide.
I guess that you have to discuss that with Toke, how he wants to handle
it ... If he gave you a patch with his signed-off-by, then you should
probably keep it? There's also "Co-developed-by" tag to give some sort
of non-author developer credits.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: yiboz@codeaurora.org
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/4] mac80211: fix issue in loop scenario
Date: Wed, 18 Dec 2019 11:18:51 +0100 [thread overview]
Message-ID: <c126d2ff0866faf9ac50b12920f0497b03b031f7.camel@sipsolutions.net> (raw)
In-Reply-To: <6f092bd44cfc581a219bd0f0506cc636@codeaurora.org>
On Wed, 2019-12-18 at 18:12 +0800, yiboz@codeaurora.org wrote:
>
> Yes, this is a fix to the first patch. Actually, the rest of two patches
> are also serve the same. So, are you suggesting to merge them to the
> first patch?
Yes.
> Previouly, I had added Toke's signature in this patch but Toke advised
> to delete it. I feel a little bit confused about how to handle it.
> Appreciate any detail guide.
I guess that you have to discuss that with Toke, how he wants to handle
it ... If he gave you a patch with his signed-off-by, then you should
probably keep it? There's also "Co-developed-by" tag to give some sort
of non-author developer credits.
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-12-18 10:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 7:19 [PATCH V4 0/4] Enable virtual time-based airtime scheduler support on ath10k Yibo Zhao
2019-12-13 7:19 ` Yibo Zhao
2019-12-13 7:19 ` [PATCH 1/4] mac80211: Switch to a virtual time-based airtime scheduler Yibo Zhao
2019-12-13 7:19 ` Yibo Zhao
2019-12-13 7:19 ` [PATCH 2/4] mac80211: fix issue in loop scenario Yibo Zhao
2019-12-13 7:19 ` Yibo Zhao
2019-12-13 9:56 ` Johannes Berg
2019-12-13 9:56 ` Johannes Berg
2019-12-18 10:12 ` yiboz
2019-12-18 10:12 ` yiboz
2019-12-18 10:18 ` Johannes Berg [this message]
2019-12-18 10:18 ` Johannes Berg
2019-12-18 10:37 ` Toke Høiland-Jørgensen
2019-12-18 10:37 ` Toke Høiland-Jørgensen
2019-12-13 7:19 ` [PATCH 3/4] mac80211: fix low throughput in multi-clients situation Yibo Zhao
2019-12-13 7:19 ` Yibo Zhao
2020-01-08 10:46 ` Justin Capella
2020-01-08 10:46 ` Justin Capella
2020-01-08 11:31 ` Toke Høiland-Jørgensen
2020-01-08 11:31 ` Toke Høiland-Jørgensen
2019-12-13 7:19 ` [PATCH 4/4] mac80211: Sync airtime weight sum with per AC synced sta airtime weight together Yibo Zhao
2019-12-13 7:19 ` Yibo Zhao
2019-12-13 9:58 ` Johannes Berg
2019-12-13 9:58 ` Johannes Berg
2019-12-17 15:20 ` Toke Høiland-Jørgensen
2019-12-17 15:20 ` Toke Høiland-Jørgensen
2019-12-13 9:03 ` [PATCH V4 0/4] Enable virtual time-based airtime scheduler support on ath10k Justin Capella
2019-12-13 9:03 ` Justin Capella
2019-12-13 10:06 ` Toke Høiland-Jørgensen
2019-12-13 10:06 ` Toke Høiland-Jørgensen
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=c126d2ff0866faf9ac50b12920f0497b03b031f7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yiboz@codeaurora.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.