[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y7/aW65pyGeebM/6@kroah.com>
Date: Thu, 12 Jan 2023 11:00:59 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Bjørn Mork <bjorn@...k.no>
Cc: Jakub Kicinski <kuba@...nel.org>,
Andre Przywara <andre.przywara@....com>,
Paolo Abeni <pabeni@...hat.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, linux-usb@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] r8152: add vendor/device ID pair for Microsoft
Devkit
On Thu, Jan 12, 2023 at 09:33:08AM +0100, Bjørn Mork wrote:
> Jakub Kicinski <kuba@...nel.org> writes:
> > On Wed, 11 Jan 2023 13:32:28 +0000 Andre Przywara wrote:
> >> The Microsoft Devkit 2023 is a an ARM64 based machine featuring a
> >> Realtek 8153 USB3.0-to-GBit Ethernet adapter. As in their other
> >> machines, Microsoft uses a custom USB device ID.
> >>
> >> Add the respective ID values to the driver. This makes Ethernet work on
> >> the MS Devkit device. The chip has been visually confirmed to be a
> >> RTL8153.
> >
> > Hm, we have a patch in net-next which reformats the entries:
> > ec51fbd1b8a2bca2948dede99c14ec63dc57ff6b
> >
> > Would you like this ID to be also added in stable? We could just
> > apply it to net, and deal with the conflict locally. But if you
> > don't care about older kernels then better if you rebase.
>
> And now I started worrying about consequences of that reformatting...
> Maybe I didn't give this enough thought?
Just send a reformatting patch for stable as well. I've taken patches
like that many times for other drivers/subsystems to make backports
trivial.
thanks,
greg k-h
Powered by blists - more mailing lists