Re: [000/241] Finish migration to Kconfig or CFG namespace

Tom Rini
2022-11-21T22:57:04Z

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

On Mon, Nov 21, 2022 at 03:51:06PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Sun, 20 Nov 2022 at 06:34, Tom Rini <trini@konsulko.com> wrote:
> >
> > Hey all,
> >
> > The intention of this series isn't to apply it just yet. This was a very
> > quick scripted migration and so there's cases where we do more than one
> > symbol, or we can see there's define but unused symbols. But it also
> > shows that with the last few series I've posted, we're nearly done. With
> > this series applied, everything builds still, and the resulting binaries
> > seem to be the same (I'm doing a build where I keep before/after so I
> > can check checksums now).
>
> It's great to see this? When will it be applied? Perhaps when -next opens up?

Everything leading up to this will go in to -next. I have a handful of
notes already on symbols that should get migrated to Kconfig or removed
outright after skimming this series, and making that be real is the next
step. Then re-running the scripted everything-else series and applying.

--
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]