From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] Remaining sunxi musb patches
Date: Tue, 02 Jun 2015 09:14:05 +0200 [thread overview]
Message-ID: <556D57BD.90502@redhat.com> (raw)
In-Reply-To: <20150601183447.GF26081@saruman.tx.rr.com>
Hi,
On 01-06-15 20:34, Felipe Balbi wrote:
> On Mon, Jun 01, 2015 at 11:30:45AM -0700, Hans de Goede wrote:
>> Hi,
>>
>> On Sunday, May 31, 2015 at 6:10:32 PM UTC+2, Hans de Goede wrote:
>>>
>>> Hi Kishon & Felipe,
>>>
>>> Here is an updated version of the remaining (not yet merged in Felipe's
>>> tree)
>>> sunxi musb patches.
>>>
>>> The "phy-sun4i-usb: Add full support for usb0 phy / OTG" patch has been
>>> updated with a small bug-fix and is ready for merging.
>>>
>>> The "musb: Add support for the Allwinner sunxi musb" patch has been
>>> updated
>>> to use the latest version of Maxime's sunxi sram controller driver. This
>>> one has a compile-time dependency on Maxime's sunxi sram controller
>>> driver,
>>> so it cannot be merged until that is merged.
>>>
>>
>>
>> Arnd has just merged the updated sram controller into the next branch
>> of the soc-drivers repo, so both these patches are now ready to merge.
>
> all right, so for v4.3 merge window there will be no issues in queues
> the two remaining patches. Thanks
So I take it that it is too late to get these 2 into 4.2 ? I've a bunch
of (small) follow up patches coming up to enable support for the musb
controller on new boards, merging those would be easier if these were
already merged. And there also is a largish set of sunxi dts patches
actually enabling the musb code which is sorta waiting for merging
these 2 (waiting for the dt binding to be stable).
If this is not going to make 4.2, can you and Kishon at least review
them and let me know of they will get merged for 4.3 as is (baring
any merge issues) ?
Regards,
Hans
next prev parent reply other threads:[~2015-06-02 7:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 16:10 [PATCH v4 0/2] Remaining sunxi musb patches Hans de Goede
2015-05-31 16:10 ` [PATCH v4 1/2] phy-sun4i-usb: Add full support for usb0 phy / OTG Hans de Goede
2015-06-01 9:22 ` Maxime Ripard
2015-06-01 9:28 ` Hans de Goede
2015-06-02 15:22 ` Maxime Ripard
2015-06-11 5:48 ` Kishon Vijay Abraham I
2015-06-11 7:56 ` [linux-sunxi] " Hans de Goede
2015-06-11 8:28 ` Hans de Goede
2015-06-11 8:07 ` Chanwoo Choi
2015-06-11 8:21 ` [linux-sunxi] " Hans de Goede
2015-06-11 8:29 ` Chanwoo Choi
2015-06-11 8:59 ` Hans de Goede
2015-06-11 9:33 ` Chanwoo Choi
2015-06-11 9:37 ` Chanwoo Choi
2015-06-11 9:38 ` Hans de Goede
2015-06-11 10:30 ` Chanwoo Choi
2015-06-11 9:42 ` Kishon Vijay Abraham I
2015-06-11 9:53 ` Hans de Goede
2015-06-11 11:16 ` Kishon Vijay Abraham I
2015-06-11 12:35 ` [linux-sunxi] " Hans de Goede
2015-06-11 12:59 ` Kishon Vijay Abraham I
2015-07-15 10:55 ` Kishon Vijay Abraham I
2015-07-15 10:58 ` Kishon Vijay Abraham I
2015-05-31 16:10 ` [PATCH v4 2/2] musb: Add support for the Allwinner sunxi musb controller Hans de Goede
2015-06-02 15:02 ` Felipe Balbi
[not found] ` <79fc4306-a621-43b8-b347-e42a27beb134@googlegroups.com>
2015-06-01 18:34 ` [PATCH v4 0/2] Remaining sunxi musb patches Felipe Balbi
2015-06-02 7:14 ` Hans de Goede [this message]
2015-06-02 14:45 ` Felipe Balbi
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=556D57BD.90502@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 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).