From: Kalle Valo <kvalo@codeaurora•org>
To: David Miller <davem@davemloft•net>
Cc: sebastian.reichel@collabora•co.uk, sre@kernel•org,
tony@atomide•com, marcel@holtmann•org, robh+dt@kernel•org,
linux-wireless@vger•kernel.org, linux-omap@vger•kernel.org,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [PATCHv4] wlcore: add wl1285 compatible
Date: Mon, 22 May 2017 17:44:24 +0300 [thread overview]
Message-ID: <87wp99t0hj.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20170522.103010.1779800840743690143.davem@davemloft.net> (David Miller's message of "Mon, 22 May 2017 10:30:10 -0400 (EDT)")
David Miller <davem@davemloft•net> writes:
> From: Kalle Valo <kvalo@codeaurora•org>
> Date: Mon, 22 May 2017 12:28:20 +0300
>
>> Sebastian Reichel <sebastian.reichel@collabora•co.uk> writes:
>>
>>> Motorola Droid 4 uses a WL1285C. With differences between the
>>> chips not being public let's add explicit binding for wl1285
>>> instead of relying on wl1283 being very similar.
>>>
>>> Reviewed-by: Rob Herring <robh@kernel•org>
>>> Acked-by: Kalle Valo <kvalo@codeaurora•org>
>>> Acked-by: Tony Lindgren <tony@atomide•com>
>>> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora•co.uk>
>>> ---
>>> Hi Dave,
>>>
>>> I previously send this in two patches, but its hard to apply without
>>> requiring multiple kernel releases (the driver must be updated before
>>> the DTS change). Since the actual change is not very complex Marcel
>>> Holtmann & Tony Lindgren suggested, that I send this directly to you
>>> in a single patch for inclusion into 4.12. This also means, that the
>>> remaining series can be queued normally for 4.13.
>>
>> I noticed that Dave set this patch to Awaiting Upstream state on his
>> patchwork:
>>
>> https://patchwork.ozlabs.org/patch/759042/
>>
>> Which makes me suspect that he is waiting me to apply this (as I
>> normally apply wlcore patches). Dave, should I actually take this patch?
>> What do you prefer?
>
> Anything that touches wireless drivers I defer to you, yes.
Thanks, I'll take it then. Not sure why Sebastian was suggested to
submit this patch via your tree in the first place.
https://patchwork.kernel.org/patch/9713645/
--
Kalle Valo
next prev parent reply other threads:[~2017-05-22 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 14:15 [PATCHv4] wlcore: add wl1285 compatible Sebastian Reichel
2017-05-22 9:28 ` Kalle Valo
[not found] ` <8737bx5jgr.fsf-5ukZ45wKbUHoml4zekdYB16hYfS7NtTn@public.gmane.org>
2017-05-22 14:30 ` David Miller
2017-05-22 14:44 ` Kalle Valo [this message]
[not found] ` <87wp99t0hj.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2017-05-22 15:21 ` Sebastian Reichel
2017-05-22 16:11 ` Rob Herring
[not found] ` <CAL_JsqL91sruKNaWmVEqT+L_OCh5xFkkGY07mBBUmqkKHc5fQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-22 16:21 ` Sebastian Reichel
2017-05-22 16:50 ` Rob Herring
[not found] ` <CAL_JsqLJ1F-2So4fSeVwR7RsUZZwMLv7HcnzHdKrOUGCU2F8+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-23 18:29 ` Sebastian Reichel
2017-05-22 15:26 ` Kalle Valo
2017-05-24 13:42 ` 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=87wp99t0hj.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=robh+dt@kernel$(echo .)org \
--cc=sebastian.reichel@collabora$(echo .)co.uk \
--cc=sre@kernel$(echo .)org \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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