All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: <ath11k@lists.infradead.org>,  <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] ath11k: Add support for SAR
Date: Fri, 01 Apr 2022 14:36:01 +0300	[thread overview]
Message-ID: <87a6d5ujby.fsf@kernel.org> (raw)
In-Reply-To: <20220401073142.1195018-1-quic_bqiang@quicinc.com> (Baochen Qiang's message of "Fri, 1 Apr 2022 15:31:42 +0800")

Baochen Qiang <quic_bqiang@quicinc.com> writes:

> This is to add support for SAR. Currently SAR is enabled
> only for WCN6855.
>
> v3:
>  1. rebased on latest ath.git
>  2. add Wen's patch "ath11k: add support for extended wmi service bit"
>     to this patch set so that there will be no dependency for the SAR patch.
> v2:
>  1. rebased on latest ath.git
>  2. add base-commit tag.
>
> Baochen Qiang (1):
>   ath11k: Add support for SAR
>
> Wen Gong (1):
>   ath11k: add support for extended wmi service bit

From looking at the timestamps I'm guessing you are submitting each
patch in a separate git send-email call? The problem with that it breaks
threading in email clients. The preference is that all mails are
submitted in one run, like in this example all patches are in foo
directory:

git format-patch -o foo master..
git send-email foo

In other words, run git send-email only once per patchset.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] ath11k: Add support for SAR
Date: Fri, 01 Apr 2022 14:36:01 +0300	[thread overview]
Message-ID: <87a6d5ujby.fsf@kernel.org> (raw)
In-Reply-To: <20220401073142.1195018-1-quic_bqiang@quicinc.com> (Baochen Qiang's message of "Fri, 1 Apr 2022 15:31:42 +0800")

Baochen Qiang <quic_bqiang@quicinc.com> writes:

> This is to add support for SAR. Currently SAR is enabled
> only for WCN6855.
>
> v3:
>  1. rebased on latest ath.git
>  2. add Wen's patch "ath11k: add support for extended wmi service bit"
>     to this patch set so that there will be no dependency for the SAR patch.
> v2:
>  1. rebased on latest ath.git
>  2. add base-commit tag.
>
> Baochen Qiang (1):
>   ath11k: Add support for SAR
>
> Wen Gong (1):
>   ath11k: add support for extended wmi service bit

From looking at the timestamps I'm guessing you are submitting each
patch in a separate git send-email call? The problem with that it breaks
threading in email clients. The preference is that all mails are
submitted in one run, like in this example all patches are in foo
directory:

git format-patch -o foo master..
git send-email foo

In other words, run git send-email only once per patchset.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2022-04-01 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  7:31 [PATCH v3 0/2] ath11k: Add support for SAR Baochen Qiang
2022-04-01  7:31 ` Baochen Qiang
2022-04-01 11:36 ` Kalle Valo [this message]
2022-04-01 11:36   ` Kalle Valo

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=87a6d5ujby.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_bqiang@quicinc.com \
    /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.