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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170704091331.GB21263@kroah.com>
Date:   Tue, 4 Jul 2017 11:13:31 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Babu Moger <babu.moger@...cle.com>,
        Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        USB list <linux-usb@...r.kernel.org>
Subject: Re: [GIT PULL] USB/PHY patches for 4.13-rc1

On Tue, Jul 04, 2017 at 11:09:36AM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
> 
> On Tue, Jul 4, 2017 at 10:04 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
> > On Tue, Jul 04, 2017 at 09:15:55AM +0200, Geert Uytterhoeven wrote:
> >> On Mon, Jul 3, 2017 at 4:58 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> >> > USB/PHY patches for 4.13-rc1
> 
> >> > 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 have no idea what happens if you enable the driver on big endian.

As I don't think anyone has USB type-c hardware for such a system, we
should be ok for now :)

thanks,

greg k-h