Re: [GIT PULL] USB/PHY patches for 4.13-rc1

[Greg KH]

On Tue, Jul 04, 2017 at 09:15:55AM +0200, Geert Uytterhoeven wrote:
> Hi Greg, Heikki,
> 
> On Mon, Jul 3, 2017 at 4:58 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> > The following changes since commit 41f1830f5a7af77cf5c86359aba3cbd706687e52:
> >
> >   Linux 4.12-rc6 (2017-06-19 22:19:37 +0800)
> >
> > are available in the git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.13-rc1
> >
> > for you to fetch changes up to 6836796de4019944f4ba4c99a360e8250fd2e735:
> >
> >   Add USB quirk for HVR-950q to avoid intermittent device resets (2017-06-29 14:49:06 +0200)
> >
> > ----------------------------------------------------------------
> > USB/PHY patches for 4.13-rc1
> >
> > Here is the big patchset of USB and PHY driver updates for 4.13-rc1.
> >
> > On the PHY side, they decided to move files around to "make things
> > easier" in their tree.  Hopefully that wasn't a mistake, but in
> > linux-next testing, we haven't had any reported problems.
> >
> > There's the usual set of gadget and xhci and musb updates in here as
> > well, along with a number of smaller updates for a raft of different USB
> > drivers.  Full details in the shortlog, nothing really major.
> >
> > All of these have been in linux-next for a while with no reported
> > issues.
> >
> > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> >
> > ----------------------------------------------------------------
> 
> > Heikki Krogerus (3):
> >       usb: typec: Add support for UCSI interface
> 
> Commit c1b0bc2dabfa884d ("usb: typec: Add support for UCSI interface"):
> 
> > --- /dev/null
> > +++ b/drivers/usb/typec/ucsi/Kconfig
> > @@ -0,0 +1,23 @@
> > +config TYPEC_UCSI
> > +       tristate "USB Type-C Connector System Software Interface driver"
> > +       depends on !CPU_BIG_ENDIAN
> 
> To work as expected, and prevent this driver from being enabled on big endian
> systems, this depends on "[PATCH v3 0/3] Define CPU_BIG_ENDIAN or warn for
> inconsistencies".
> https://lkml.org/lkml/2017/6/12/1068

Is this a problem?  I thought that series was slated to be merged soon,
is that not going to happen?

thanks,

greg k-h