[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170521114725.GR8541@lahna.fi.intel.com>
Date: Sun, 21 May 2017 14:47:25 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: "Bernat, Yehezkel" <yehezkel.bernat@...el.com>
Cc: "Levy, Amir (Jer)" <amir.jer.levy@...el.com>,
Lukas Wunner <lukas@...ner.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andreas Noever <andreas.noever@...il.com>,
"Jamet, Michael" <michael.jamet@...el.com>,
Andy Lutomirski <luto@...nel.org>,
"Mario.Limonciello@...l.com" <Mario.Limonciello@...l.com>,
"Jared.Dominguez@...l.com" <Jared.Dominguez@...l.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 18/24] thunderbolt: Store Thunderbolt generation in the
switch structure
On Sun, May 21, 2017 at 11:18:01AM +0000, Bernat, Yehezkel wrote:
> Nothing that I'm aware of.
OK.
> Still, I like the idea of having a table-like construct somewhere in
> the code to centralize the handling of various controller-specific
> info (generation, DMA port, maybe more things in the future).
Yup, I guess that's something we could try out in the next version of
the series.
Powered by blists - more mailing lists