From: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2] ath10k: add tracing for frame transmission
Date: Wed, 8 Oct 2014 08:29:38 +0530 [thread overview]
Message-ID: <20141008025936.GA3116@qca.qualcomm.com> (raw)
In-Reply-To: <87lhoshrwh.fsf@kamboji.qca.qualcomm.com>
On Tue, Oct 07, 2014 at 05:32:30PM +0300, Kalle Valo wrote:
> Rajkumar Manoharan <rmanohar@qti.qualcomm.com> writes:
>
> > Add tracing support to forward management and data frames to
> > user space for packet inspection.
> >
> > Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
>
> ! [ 80: Rajkumar Manoharan ] [PATCH 1/2] ath10k: add tracepoint for htt tx frames
> ! [ 105: Rajkumar Manoharan ] [PATCH 2/2] ath10k: add tracing for frame transmission
>
> For the future: it's a lot easier if you add a cover letter for the
> patch series, keep the cover letter title unchanged and just increase
> the version number after each revision. That way I can immeaditely see
> what patches I should take or ignore.
>
I replied to series to ignore the patchset. Sorry if the message is not
clear. In next version, I combined both patches.
-Rajkumar
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] ath10k: add tracing for frame transmission
Date: Wed, 8 Oct 2014 08:29:38 +0530 [thread overview]
Message-ID: <20141008025936.GA3116@qca.qualcomm.com> (raw)
In-Reply-To: <87lhoshrwh.fsf@kamboji.qca.qualcomm.com>
On Tue, Oct 07, 2014 at 05:32:30PM +0300, Kalle Valo wrote:
> Rajkumar Manoharan <rmanohar@qti.qualcomm.com> writes:
>
> > Add tracing support to forward management and data frames to
> > user space for packet inspection.
> >
> > Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
>
> ! [ 80: Rajkumar Manoharan ] [PATCH 1/2] ath10k: add tracepoint for htt tx frames
> ! [ 105: Rajkumar Manoharan ] [PATCH 2/2] ath10k: add tracing for frame transmission
>
> For the future: it's a lot easier if you add a cover letter for the
> patch series, keep the cover letter title unchanged and just increase
> the version number after each revision. That way I can immeaditely see
> what patches I should take or ignore.
>
I replied to series to ignore the patchset. Sorry if the message is not
clear. In next version, I combined both patches.
-Rajkumar
next prev parent reply other threads:[~2014-10-08 2:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 17:09 [PATCH v2] ath10k: add tracing for frame transmission Rajkumar Manoharan
2014-10-06 17:09 ` Rajkumar Manoharan
2014-10-07 14:32 ` Kalle Valo
2014-10-07 14:32 ` Kalle Valo
2014-10-08 2:59 ` Rajkumar Manoharan [this message]
2014-10-08 2:59 ` Rajkumar Manoharan
2014-10-07 16:19 ` Kalle Valo
2014-10-07 16:19 ` Kalle Valo
2014-10-08 3:13 ` Rajkumar Manoharan
2014-10-08 3:13 ` Rajkumar Manoharan
2014-10-08 10:19 ` Kalle Valo
2014-10-08 10:19 ` Kalle Valo
2014-10-08 10:27 ` Kalle Valo
2014-10-08 10:27 ` 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=20141008025936.GA3116@qca.qualcomm.com \
--to=rmanohar@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.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.