[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1569947262.2639.15.camel@suse.com>
Date: Tue, 01 Oct 2019 18:27:42 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Anthony Wong <anthony.wong@...onical.com>,
Mario.Limonciello@...l.com,
Andreas Noever <andreas.noever@...il.com>,
Yehezkel Bernat <YehezkelShB@...il.com>,
Michael Jamet <michael.jamet@...el.com>,
Rajmohan Mani <rajmohan.mani@...el.com>,
Nicholas Johnson <nicholas.johnson-opensource@...look.com.au>,
Alan Stern <stern@...land.harvard.edu>,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
Lukas Wunner <lukas@...ner.de>
Subject: Re: [RFC PATCH 17/22] thunderbolt: Add initial support for USB4
Am Dienstag, den 01.10.2019, 18:07 +0300 schrieb Mika Westerberg:
Hi,
> OK, but does that break existing .configs? I mean if you have already
> CONFIG_THUNDERBOLT in your .config/defconfig does it now just get
> dropped silently?
People will have to look at this new stuff anyway.
> For example firewire has CONFIG_FIREWIRE even though the "standard" name
> is IEEE 1394. I was thinking maybe we can do the same for
> USB4/Thunderbolt
USB and Thunderbolt used to be distinct protocols. Whereas Firewire
was just a colloquial name for IEEE1394. Please be wordy here.
"Unified support for USB4 and Thunderbolt4"
Regards
Oliver
Powered by blists - more mailing lists