Re: [PATCH 1/4] add generic builtin command line
On Mon, 15 Feb 2021 11:32:01 -0800 Daniel Gimpelevich wrote: > On Thu, 2019-03-21 at 15:15 -0700, Andrew Morton wrote: > > On Thu, 21 Mar 2019 08:13:08 -0700 Daniel Walker wrote: > > > On Wed, Mar 20, 2019 at 08:14:33PM -0700, Andrew Morton wrote: > > > > The patches (or some version of them) are already in linux-next, > > > > which messes me up. I'll disable them for now. > > > > > > Those are from my tree, but I remove them when you picked up the series. > > > The > > > next linux-next should not have them. > > > > Yup, thanks, all looks good now. > > This patchset is currently neither in mainline nor in -next. May I ask > what happened to it? Thanks. Seems that I didn't bring them back after the confict with the powerpc tree resolved itself. Please resend everything for -rc1 and let's await the reviewer feedback,
Re: [PATCH 1/4] add generic builtin command line
On Tue, 2021-02-16 at 18:42 +0100, Christophe Leroy wrote: > I'd suggest also to find the good arguments to convince us that this > series has a real added value, not just "cisco use it in its kernels > so it is good". Well, IIRC, this series was endorsed by the device tree maintainers as the preferred alternative to this: https://lore.kernel.org/linux-devicetree/1565020400-25679-1-git-send-email-dan...@gimpelevich.san-francisco.ca.us/T/#u The now-defunct patchwork.linux-mips.org link in that thread pointed to: https://lore.kernel.org/linux-mips/1510796793.16864.25.camel@chimera/T/#u When running modern kernels from ancient vendor bootloaders, it is sometimes necessary to pick and choose bits and pieces of the info they pass without taking it verbatim.
Re: [PATCH 1/4] add generic builtin command line
On Mon, Feb 15, 2021 at 11:32:01AM -0800, Daniel Gimpelevich wrote: > On Thu, 2019-03-21 at 15:15 -0700, Andrew Morton wrote: > > On Thu, 21 Mar 2019 08:13:08 -0700 Daniel Walker wrote: > > > On Wed, Mar 20, 2019 at 08:14:33PM -0700, Andrew Morton wrote: > > > > The patches (or some version of them) are already in linux-next, > > > > which messes me up. I'll disable them for now. > > > > > > Those are from my tree, but I remove them when you picked up the series. > > > The > > > next linux-next should not have them. > > > > Yup, thanks, all looks good now. > > This patchset is currently neither in mainline nor in -next. May I ask > what happened to it? Thanks. > It was dropped silently by Andrew at some point. I wasn't watching -next closely to know when. I have no idea why he dropped it. We still use this series extensively in Cisco, and have extended it beyond this current series. We can re-submit. Daniel
Re: [PATCH 1/4] add generic builtin command line
Daniel Gimpelevich a écrit : On Thu, 2019-03-21 at 15:15 -0700, Andrew Morton wrote: On Thu, 21 Mar 2019 08:13:08 -0700 Daniel Walker wrote: > On Wed, Mar 20, 2019 at 08:14:33PM -0700, Andrew Morton wrote: > > The patches (or some version of them) are already in linux-next, > > which messes me up. I'll disable them for now. > > Those are from my tree, but I remove them when you picked up the series. The > next linux-next should not have them. Yup, thanks, all looks good now. This patchset is currently neither in mainline nor in -next. May I ask what happened to it? Thanks. As far as I remember, there has been a lot of discussion around this series. As of today, it doesn't apply cleanly anymore and would require rebasing. I'd suggest also to find the good arguments to convince us that this series has a real added value, not just "cisco use it in its kernels so it is good". I proposed an alternative at https://patchwork.ozlabs.org/project/linuxppc-dev/cover/cover.1554195798.git.christophe.le...@c-s.fr/ but never got any feedback so I gave up. If you submit a new series, don't forget to copy ppclinux-dev and linux-arch lists. Christophe
Re: [PATCH 1/4] add generic builtin command line
On Thu, 2019-03-21 at 15:15 -0700, Andrew Morton wrote: > On Thu, 21 Mar 2019 08:13:08 -0700 Daniel Walker wrote: > > On Wed, Mar 20, 2019 at 08:14:33PM -0700, Andrew Morton wrote: > > > The patches (or some version of them) are already in linux-next, > > > which messes me up. I'll disable them for now. > > > > Those are from my tree, but I remove them when you picked up the series. The > > next linux-next should not have them. > > Yup, thanks, all looks good now. This patchset is currently neither in mainline nor in -next. May I ask what happened to it? Thanks.
