From: Christoph Hellwig <hch@lst.de>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] unicode: clean up the Kconfig symbol confusion
Date: Mon, 31 Jan 2022 07:44:44 +0100 [thread overview]
Message-ID: <20220131064444.GA4745@lst.de> (raw)
In-Reply-To: <20220124090855.GA23041@lst.de>
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@linux-foundation.org>
> > > Signed-off-by: Christoph Hellwig <hch@lst.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?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] unicode: clean up the Kconfig symbol confusion
Date: Mon, 31 Jan 2022 07:44:44 +0100 [thread overview]
Message-ID: <20220131064444.GA4745@lst.de> (raw)
In-Reply-To: <20220124090855.GA23041@lst.de>
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@linux-foundation.org>
> > > Signed-off-by: Christoph Hellwig <hch@lst.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?
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-01-31 6:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 6:56 [PATCH] unicode: clean up the Kconfig symbol confusion Christoph Hellwig
2022-01-18 6:56 ` [f2fs-dev] " Christoph Hellwig
2022-01-18 19:00 ` Eric Biggers
2022-01-18 19:00 ` [f2fs-dev] " Eric Biggers
2022-01-19 8:28 ` [PATCH] " Linus Torvalds
2022-01-19 8:28 ` [f2fs-dev] " Linus Torvalds
2022-01-21 1:10 ` Gabriel Krisman Bertazi
2022-01-21 1:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-01-24 9:08 ` Christoph Hellwig
2022-01-24 9:08 ` [f2fs-dev] " Christoph Hellwig
2022-01-31 6:44 ` Christoph Hellwig [this message]
2022-01-31 6:44 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220131064444.GA4745@lst.de \
--to=hch@lst.de \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.