From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>, Tony Lindgren <tony@atomide.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>,
Uri Mashiach <uri.mashiach@compulab.co.il>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, <bcousson@baylibre.com>,
Eliad Peller <eliad@wizery.com>, <devicetree@vger.kernel.org>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] wlcore/wl12xx: spi: add wifi support to cm-t335
Date: Thu, 14 Jan 2016 10:08:24 +0100 [thread overview]
Message-ID: <56976588.3060707@broadcom.com> (raw)
In-Reply-To: <87wprcbpyr.fsf@kamboji.qca.qualcomm.com>
On 01/14/2016 08:05 AM, Kalle Valo wrote:
> Tony Lindgren <tony@atomide.com> writes:
>
>>>>> arch/arm/boot/dts/am335x-cm-t335.dts | 55 ++++++++++++++++++++++++++++++++++++
>>>>> 1 file changed, 55 insertions(+)
>>>>
>>>> To what tree should this patch go? My wireless-drivers-next tree doesn't
>>>> even have this file.
>>>
>>> Right. It will hit the mainline during this merge window through Tony's and
>>> arm-soc trees.
>>>
>>> Do you think it will be sensible if you take 1/3 and 2/3 patches and Tony
>>> will take the 3/3 (there is no code dependency between first two and the last one),
>>> or we can just wait till arm-soc hits the mainline, so you will have the
>>> needed code?
>>
>> Yeah I'll pick the dts changes separately after the merge window as
>> there is no dependency to the driver changes.
>
> Ok, I'll then take patches 1 and 2 once the merge window opens.
I guess it is semantics, but the merge window is open right now so you
probably mean to say after the merge window closes, ie. when 4.5-rc1 is
ready.
Regards,
Arend
next prev parent reply other threads:[~2016-01-14 9:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 13:35 [PATCH v4 0/3] wlcore/wl12xx: spi: add wifi support to cm-t335 Uri Mashiach
2015-12-30 13:35 ` [PATCH v4 1/3] wlcore/wl12xx: spi: add power operation function Uri Mashiach
2016-01-09 2:53 ` Sebastian Reichel
2016-01-12 11:21 ` Grygorii Strashko
2016-01-13 6:03 ` Igor Grinberg
2016-01-29 9:11 ` [v4,1/3] " Kalle Valo
2015-12-30 13:35 ` [PATCH v4 2/3] wlcore/wl12xx: spi: add device tree support Uri Mashiach
2016-01-09 2:56 ` Sebastian Reichel
2016-01-12 11:24 ` Grygorii Strashko
2016-01-13 6:05 ` Igor Grinberg
2015-12-30 13:35 ` [PATCH v4 3/3] wlcore/wl12xx: spi: add wifi support to cm-t335 Uri Mashiach
2016-01-07 9:02 ` Kalle Valo
2016-01-07 11:20 ` Uri Mashiach
2016-01-13 6:00 ` Igor Grinberg
2016-01-13 17:27 ` Tony Lindgren
2016-01-14 7:05 ` Kalle Valo
2016-01-14 9:08 ` Arend van Spriel [this message]
2016-01-14 9:11 ` Kalle Valo
2016-01-27 18:40 ` Tony Lindgren
2016-01-13 6:09 ` Igor Grinberg
2016-01-27 18:41 ` Tony Lindgren
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=56976588.3060707@broadcom.com \
--to=arend@broadcom.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=eliad@wizery.com \
--cc=galak@codeaurora.org \
--cc=grinberg@compulab.co.il \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=uri.mashiach@compulab.co.il \
/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;
as well as URLs for NNTP newsgroup(s).