[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqKjS1TgCtcy_L3X5g54JDheF9PEF9tGE=SZR1H=NWP6Mg@mail.gmail.com>
Date: Mon, 30 Oct 2023 08:56:09 -0500
From: Rob Herring <robh@...nel.org>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: Wolfgang Grandegger <wg@...ndegger.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Appana Durga Kedareswara rao <appana.durga.rao@...inx.com>,
Naga Sureshkumar Relli <naga.sureshkumar.relli@...inx.com>,
Michal Simek <michal.simek@....com>, linux-can@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next] net: can: Use device_get_match_data()
On Tue, Oct 10, 2023 at 7:02 AM Marc Kleine-Budde <mkl@...gutronix.de> wrote:
>
> On 09.10.2023 12:29:02, Rob Herring wrote:
> > Use preferred device_get_match_data() instead of of_match_device() to
> > get the driver match data. With this, adjust the includes to explicitly
> > include the correct headers.
> >
> > Signed-off-by: Rob Herring <robh@...nel.org>
>
> Applied to linux-can-next/testing.
Still not seeing this in linux-next. Did it get lost?
Rob
Powered by blists - more mailing lists