Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: linux-wireless@vger.kernel.org,
	sergey.matyukevich.os@quantenna.com, avinashp@quantenna.com,
	johannes@sipsolutions.net
Subject: Re: [V2, 1/9] qtnfmac: qlink: convert channel width from bitfiled to simple enum
Date: Wed, 20 Sep 2017 12:23:14 +0000 (UTC)	[thread overview]
Message-ID: <20170920122314.5397A60710@smtp.codeaurora.org> (raw)
In-Reply-To: <20170902014451.17766-2-igor.mitsyanko.os@quantenna.com>

Igor Mitsyanko <igor.mitsyanko.os@quantenna.com> wrote:

> From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
> 
> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
> Reviewed-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>

No empty commit logs, please. After the first patch I was about to write
one myself but after seeing multiple of them I'm not going to do that.

9 patches set to Changes Requested.

9935431 [V2,1/9] qtnfmac: qlink: convert channel width from bitfiled to simple enum
9935437 [V2,2/9] qtnfmac: make "Channel change" event report full channel info
9935443 [V2,3/9] qtnfmac: retrieve current channel info from EP
9935445 [V2,4/9] qtnfmac: do not cache channel info from "connect" command
9935429 [V2,5/9] qtnfmac: let wifi card handle channel switch request to the same chan
9935441 [V2,6/9] qtnfmac: pass VIF info to SendChannel command
9935433 [V2,7/9] qtnfmac: do not cache CSA chandef info
9935439 [V2,8/9] qtnfmac: remove unused mac::status field
9935435 [V2,9/9] qtnfmac: do not report channel changes until wiphy is registered

-- 
https://patchwork.kernel.org/patch/9935431/

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

  parent reply	other threads:[~2017-09-20 12:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-02  1:44 [PATCH V2 0/9] qtnfmac: more info on current channel from device igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 1/9] qtnfmac: qlink: convert channel width from bitfiled to simple enum igor.mitsyanko.os
2017-09-04 11:31   ` Sergey Matyukevich
2017-09-20 12:23   ` Kalle Valo [this message]
2017-09-20 12:33     ` [V2, " Kalle Valo
2017-09-20 15:33       ` Sergey Matyukevich
2017-09-02  1:44 ` [PATCH V2 2/9] qtnfmac: make "Channel change" event report full channel info igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 3/9] qtnfmac: retrieve current channel info from EP igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 4/9] qtnfmac: do not cache channel info from "connect" command igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 5/9] qtnfmac: let wifi card handle channel switch request to the same chan igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 6/9] qtnfmac: pass VIF info to SendChannel command igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 7/9] qtnfmac: do not cache CSA chandef info igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 8/9] qtnfmac: remove unused mac::status field igor.mitsyanko.os
2017-09-02  1:44 ` [PATCH V2 9/9] qtnfmac: do not report channel changes until wiphy is registered igor.mitsyanko.os

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=20170920122314.5397A60710@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=avinashp@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sergey.matyukevich.os@quantenna.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox