Re: [RFC PATCH 0/4] dm: Duplicate uclass name fix and alias improvements

Hi Simon, On Thu, Aug 1, 2024 at 4:42 PM Simon Glass wrote: > > Can we rename the gadget uclass to usb_gadget or similar, then update > the aliases? > You mean split patch no.4 into 2 parts, first rename the class to usb_gadget before doing the alias job ? > I think it makes sense to show the s

Re: [RFC PATCH 0/4] dm: Duplicate uclass name fix and alias improvements

Hi Zixun, On Thu, 1 Aug 2024 at 12:37, Zixun LI wrote: > > Hi Simon, > > On Thu, Aug 1, 2024 at 4:42 PM Simon Glass wrote: > > > > Can we rename the gadget uclass to usb_gadget or similar, then update > > the aliases? > > > > You mean split patch no.4 into 2 parts, first rename the class to usb_

Re: [RFC PATCH 0/4] dm: Duplicate uclass name fix and alias improvements

Hi Zixun, On Wed, 31 Jul 2024 at 07:43, Zixun LI wrote: > > Patch 1 is a tentative fix for duplicate uclass name issue met in > https://lists.denx.de/pipermail/u-boot/2024-July/560189.html > > The idea is to use orignal class name only for sequence alias to keep this > alias function working and

[RFC PATCH 0/4] dm: Duplicate uclass name fix and alias improvements

Patch 1 is a tentative fix for duplicate uclass name issue met in https://lists.denx.de/pipermail/u-boot/2024-July/560189.html The idea is to use orignal class name only for sequence alias to keep this alias function working and rename the class something else. Patch 2 and 3 make "dm tree", "bind