From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: [GIT,PULL] USB: changes for v4.16 merge window
Date: Tue, 09 Jan 2018 10:47:02 +0200 [thread overview]
Message-ID: <87fu7fzaex.fsf@linux.intel.com> (raw)
Hi,
Alan Stern <stern@rowland.harvard.edu> writes:
> On Mon, 8 Jan 2018, Felipe Balbi wrote:
>
>>
>> Hi Greg,
>>
>> Here are my changes for this merge window. Let me know if you want
>> anything to be changed.
>>
>> Patches have been on linux-next for quite a while ;-)
>>
>> cheers
>>
>> The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
>>
>> Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git usb-for-v4.16
>>
>> for you to fetch changes up to 8ada211d0383b72878582bd312b984a9eae62b30:
>>
>> usb: renesas_usbhs: add extcon notifier to set mode for non-otg channel (2017-12-14 09:57:38 +0200)
>>
>> ----------------------------------------------------------------
>> usb: changes for v4.16 merge window
>>
>> Not many changes here, the most important being an improvement for TI's
>> AM57xx and DRA7xx devices which allows them to disable a metastability
>> workaround in situations where we know what's going on.
>>
>> Other than that, we have a set of changes on Renesas UDC to make the
>> code a little easier to read and maintain while also better supporting
>> extcon framework.
>>
>> The u_serial adaptation layer learned to use kfifo instead of cooking
>> its own FIFO implementation.
>>
>> DWC3 learned to decode a few more USB requests on the trace output.
>>
>> ----------------------------------------------------------------
>
> Felipe, have you looked at my patch submitted on Jan. 3 (USB: UDC core:
> fix double-free in usb_add_gadget_udc_release)?
>
> https://marc.info/?l=linux-usb&m=151500192800372&w=2
>
> Was it just too late to fit into your 4.16 time frame?
I just missed it because of my 3 weeks out of office. I can pick it up
during the -rc unless Greg wants to take it by hand if it's super
important.
next reply other threads:[~2018-01-09 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 8:47 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 9:04 [GIT,PULL] USB: changes for v4.16 merge window Greg Kroah-Hartman
2018-01-08 15:54 Alan Stern
2018-01-08 13:17 Greg Kroah-Hartman
2018-01-08 11:48 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=87fu7fzaex.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).