From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Douglas Anderson <dianders@chromium.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Matthias Kaehlcke <mka@chromium.org>,
Ryan Case <ryandcase@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
"David S. Miller" <davem@davemloft.net>,
Ganapathi Bhat <gbhat@marvell.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <amitkarwar@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Nishant Sarmukadam <nishants@marvell.com>,
"<netdev@vger.kernel.org>" <netdev@vger.kernel.org>,
Xinming Hu <huxinming820@gmail.com>
Subject: Re: [PATCH] mwifiex: Make resume actually do something useful again on SDIO cards
Date: Fri, 05 Apr 2019 06:35:39 +0300 [thread overview]
Message-ID: <87ef6hruno.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+ASDXNfOUmMEWYwts8PuiDaEjuoPK+tZ0BhDSSte5u5toydkA@mail.gmail.com> (Brian Norris's message of "Thu, 4 Apr 2019 13:47:17 -0700")
Brian Norris <briannorris@chromium.org> writes:
> On Wed, Apr 3, 2019 at 10:20 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>> Douglas Anderson <dianders@chromium.org> writes:
>> > Fixes: fc3a2fcaa1ba ("mwifiex: use atomic bitops to represent
>> > adapter status variables")
>> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
>>
>> I'm planning to queue this for 5.1.
>
> With an explicit
>
> Cc: <stable@vger.kernel.org>
>
> please? Somebody would likely pick it up anyway, but it's nice to be
> explicit.
Ok, I'll add that.
> Not that it really matters, but also:
>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
This patchwork picks up automatically so I don't have to do anything.
But I so wish it would do the same for Cc and Fixes tags :)
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Douglas Anderson <dianders@chromium.org>,
"open list\:ARM\/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Matthias Kaehlcke <mka@chromium.org>,
Ryan Case <ryandcase@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
"David S. Miller" <davem@davemloft.net>,
Ganapathi Bhat <gbhat@marvell.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <amitkarwar@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Nishant Sarmukadam <nishants@marvell.com>,
"\<netdev\@vger.kernel.org\>" <netdev@vger.kernel.org>,
Xinming Hu <huxinming820@gmail.com>
Subject: Re: [PATCH] mwifiex: Make resume actually do something useful again on SDIO cards
Date: Fri, 05 Apr 2019 06:35:39 +0300 [thread overview]
Message-ID: <87ef6hruno.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+ASDXNfOUmMEWYwts8PuiDaEjuoPK+tZ0BhDSSte5u5toydkA@mail.gmail.com> (Brian Norris's message of "Thu, 4 Apr 2019 13:47:17 -0700")
Brian Norris <briannorris@chromium.org> writes:
> On Wed, Apr 3, 2019 at 10:20 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>> Douglas Anderson <dianders@chromium.org> writes:
>> > Fixes: fc3a2fcaa1ba ("mwifiex: use atomic bitops to represent
>> > adapter status variables")
>> > Signed-off-by: Douglas Anderson <dianders@chromium.org>
>>
>> I'm planning to queue this for 5.1.
>
> With an explicit
>
> Cc: <stable@vger.kernel.org>
>
> please? Somebody would likely pick it up anyway, but it's nice to be
> explicit.
Ok, I'll add that.
> Not that it really matters, but also:
>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
This patchwork picks up automatically so I don't have to do anything.
But I so wish it would do the same for Cc and Fixes tags :)
--
Kalle Valo
next prev parent reply other threads:[~2019-04-05 3:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 4:01 [PATCH] mwifiex: Make resume actually do something useful again on SDIO cards Douglas Anderson
2019-04-04 5:20 ` Kalle Valo
[not found] ` <874l7egxdj.fsf-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2019-04-04 20:47 ` Brian Norris
2019-04-04 20:47 ` Brian Norris
2019-04-05 3:35 ` Kalle Valo [this message]
2019-04-05 3:35 ` Kalle Valo
[not found] ` <87ef6hruno.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2019-04-18 16:31 ` Doug Anderson
2019-04-18 16:31 ` Doug Anderson
[not found] ` <CAD=FV=WgTUgMg-r2ZJ6rKOiv5Lw_m-EX6c0it6znA9v8AO+z_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-04-19 4:03 ` Kalle Valo
2019-04-19 4:03 ` Kalle Valo
[not found] ` <20190404040106.40519-1-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2019-04-25 11:05 ` Kalle Valo
2019-04-25 11:05 ` Kalle Valo
2019-04-25 11:05 ` 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=87ef6hruno.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=amitkarwar@gmail.com \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=gbhat@marvell.com \
--cc=heiko@sntech.de \
--cc=huxinming820@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=ryandcase@chromium.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.