From: Kalle Valo <kvalo@kernel.org>
To: "Aditya Kumar Singh \(QUIC\)" <quic_adisi@quicinc.com>
Cc: "Jeff Johnson \(QUIC\)" <quic_jjohnson@quicinc.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PATCH 1/2] ath11k: move firmware stats out of debugfs
Date: Fri, 03 Jun 2022 13:37:54 +0300 [thread overview]
Message-ID: <87r146m3r1.fsf@kernel.org> (raw)
In-Reply-To: <DM5PR0201MB3589A92F02DBAA0A26B8BF8684A19@DM5PR0201MB3589.namprd02.prod.outlook.com> (Aditya Kumar Singh's message of "Fri, 3 Jun 2022 04:23:04 +0000")
"Aditya Kumar Singh (QUIC)" <quic_adisi@quicinc.com> writes:
> Sure, will address in v2. Thanks for pointing out.
Please edit your quotes. You had over 500 lines of quotes in your one
line reply, this makes it horrible to use patchwork:
https://patchwork.kernel.org/project/linux-wireless/patch/20220602051425.9265-2-quic_adisi@quicinc.com/
--
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: "Aditya Kumar Singh \(QUIC\)" <quic_adisi@quicinc.com>
Cc: "Jeff Johnson \(QUIC\)" <quic_jjohnson@quicinc.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PATCH 1/2] ath11k: move firmware stats out of debugfs
Date: Fri, 03 Jun 2022 13:37:54 +0300 [thread overview]
Message-ID: <87r146m3r1.fsf@kernel.org> (raw)
In-Reply-To: <DM5PR0201MB3589A92F02DBAA0A26B8BF8684A19@DM5PR0201MB3589.namprd02.prod.outlook.com> (Aditya Kumar Singh's message of "Fri, 3 Jun 2022 04:23:04 +0000")
"Aditya Kumar Singh (QUIC)" <quic_adisi@quicinc.com> writes:
> Sure, will address in v2. Thanks for pointing out.
Please edit your quotes. You had over 500 lines of quotes in your one
line reply, this makes it horrible to use patchwork:
https://patchwork.kernel.org/project/linux-wireless/patch/20220602051425.9265-2-quic_adisi@quicinc.com/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-06-03 10:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 5:14 [PATCH 0/2] ath11k: add support for get_txpower mac ops Aditya Kumar Singh
2022-06-02 5:14 ` Aditya Kumar Singh
2022-06-02 5:14 ` [PATCH 1/2] ath11k: move firmware stats out of debugfs Aditya Kumar Singh
2022-06-02 5:14 ` Aditya Kumar Singh
2022-06-02 14:33 ` Jeff Johnson
2022-06-02 14:33 ` Jeff Johnson
2022-06-03 4:23 ` Aditya Kumar Singh (QUIC)
2022-06-03 4:23 ` Aditya Kumar Singh (QUIC)
2022-06-03 10:37 ` Kalle Valo [this message]
2022-06-03 10:37 ` Kalle Valo
2022-06-03 6:50 ` Kalle Valo
2022-06-03 6:50 ` Kalle Valo
2022-06-03 8:30 ` Aditya Kumar Singh (QUIC)
2022-06-03 8:30 ` Aditya Kumar Singh (QUIC)
2022-06-02 5:14 ` [PATCH 2/2] ath11k: add get_txpower mac ops Aditya Kumar Singh
2022-06-02 5:14 ` Aditya Kumar Singh
2022-06-02 14:51 ` Jeff Johnson
2022-06-02 14:51 ` Jeff Johnson
2022-06-03 4:41 ` Aditya Kumar Singh (QUIC)
2022-06-03 4:41 ` Aditya Kumar Singh (QUIC)
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=87r146m3r1.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@quicinc.com \
--cc=quic_jjohnson@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.