mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Babu Moger <babu.moger@oracle.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Max Filippov <jcmvbkbc@gmail.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: [GIT PULL] USB/PHY patches for 4.13-rc1
Date: Tue, 4 Jul 2017 12:19:07 -0500	[thread overview]
Message-ID: <df3533e1-47a8-d6f3-293b-bd0245eaaf25@oracle.com> (raw)
In-Reply-To: <CAMuHMdVndyuSSvBN+xPgQXAuEYLLRvS-fY0K4JnvVpw_qmu8QQ@mail.gmail.com>



On 7/4/2017 4:09 AM, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Tue, Jul 4, 2017 at 10:04 AM, Greg KH <gregkh@linuxfoundation.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@linuxfoundation.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.
>
>> I thought that series was slated to be merged soon,
>> is that not going to happen?
> Me too. But it's not in next-20170704.
>
> Babu, what's the plan?

Yes. I  think these series are safe to be merged.

Max, Do you have any concerns about xtensa?

>
> Thanks!
>
> Gr{oetje,eeting}s,
>
>                          Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                  -- Linus Torvalds

  parent reply	other threads:[~2017-07-04 17:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 14:58 Greg KH
2017-07-04  1:27 ` Stephen Rothwell
2017-07-04  7:15 ` Geert Uytterhoeven
2017-07-04  8:04   ` Greg KH
2017-07-04  9:09     ` Geert Uytterhoeven
2017-07-04  9:13       ` Greg KH
2017-07-04 10:33         ` Geert Uytterhoeven
2017-07-04 17:19       ` Babu Moger [this message]
2017-07-06  8:24         ` Max Filippov
2017-07-06 14:28           ` Babu Moger
2017-07-06 14:33             ` Greg KH
2017-07-06 15:28               ` Babu Moger
2017-07-06 15:51                 ` Greg KH
2017-07-06 15:54                   ` Babu Moger

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=df3533e1-47a8-d6f3-293b-bd0245eaaf25@oracle.com \
    --to=babu.moger@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®