On Wed, Feb 29, 2012 at 11:55:00AM +0200, Felipe Balbi wrote: > Hi Greg, > > Here's an updated pull request. Please consider pulling. Let me know if > there are still any concerns. > > The following changes since commit 62aa2b537c6f5957afd98e29f96897419ed5ebab: > > Linux 3.3-rc2 (2012-01-31 13:31:54 -0800) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git tags/dwc3-for-v3.4 > > for you to fetch changes up to 87e3782faa9c5777f4054833f71f9203d2cde2a2: > > usb: dwc3: clear 'res_trans_idx' as soon as it becomes invalid (2012-02-27 16:30:52 +0200) > > ---------------------------------------------------------------- > Here are the changes for v3.4 merge window. Better, but next time, care to at least say what type of changes in a prefix? I edited the first line of this to say: USB: DWC3: Here are the changes for v3.4 merge window. > It includes a new glue layer for Samsung's Exynos platform, a simplification of > memory management on DWC3 driver by using dev_xxx functions, a few > optimizations to IRQ handling by dropping memcpy() and using bitshifts, a fix > for TI's OMAP5430 TX Fifo Allocation, two fixes to test mode implementation > (one on debugfs and one on ep0), and several minor changes such as whitespace > cleanups, simplification of a few parts of the code, decreasing a long delay to > something a bit saner, dropping a header which was included twice and so on. > > The highlight on this merge is the support for Samsung's Exynos platform, > increasing the number of different users for this driver to three. > I know it's not needed, well, maybe it should be, but in the future, could you also put a signed-off-by in here? For some reason, the author of the tag comments aren't showing up in the commit log, it shows up as me, and it would be good to at least know who wrote this. Anyway, no big deal, I'll go ask the git developers about this one... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
