[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220131064444.GA4745@lst.de>
Date: Mon, 31 Jan 2022 07:44:44 +0100
From: Christoph Hellwig <hch@....de>
To: Gabriel Krisman Bertazi <krisman@...labora.com>
Cc: Christoph Hellwig <hch@....de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [PATCH] unicode: clean up the Kconfig symbol confusion
On Mon, Jan 24, 2022 at 10:08:55AM +0100, Christoph Hellwig wrote:
> On Thu, Jan 20, 2022 at 08:10:47PM -0500, Gabriel Krisman Bertazi wrote:
> > > Fixes: 2b3d04787012 ("unicode: Add utf8-data module")
> > > Reported-by: Linus Torvalds <torvalds@...ux-foundation.org>
> > > Signed-off-by: Christoph Hellwig <hch@....de>
> >
> > I fixed the typo and pushed the patch to a linux-next visible branch
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git/commit/?h=for-next&id=5298d4bfe80f6ae6ae2777bcd1357b0022d98573
> >
> > I'm also sending a patch series shortly turning IS_ENABLED into part of
> > the code flow where possible.
>
> Thanks. It might make sense to get the one patch to Linux for 5.17
> so that we don't have the new Kconfig symbol for just one release.
Can we try to get this into 5.17-rc, please to avoid adding the Kconfig
symbol Linus complained about in one release just to remove it again
in the next one?
Powered by blists - more mailing lists