From: "Pali Rohár" <pali@kernel.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jan Kara <jack@suse.cz>, Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [RFC PATCH 3/3] nls: Replace default nls table by correct iso8859-1 table
Date: Sat, 4 Feb 2023 11:58:07 +0100	[thread overview]
Message-ID: <20230204105807.jdd2rrrzf37hns6h@pali> (raw)
In-Reply-To: <87v8leu4iy.fsf@mail.parknet.co.jp>
On Tuesday 10 January 2023 18:23:33 OGAWA Hirofumi wrote:
> Pali Rohár <pali@kernel.org> writes:
> 
> [...]
> 
> > -static struct nls_table default_table = {
> > -	.charset	= "default",
> > +static struct nls_table iso8859_1_table = {
> > +	.charset	= "iso8859-1",
> >  	.uni2char	= uni2char,
> >  	.char2uni	= char2uni,
> >  	.charset2lower	= charset2lower,
> >  	.charset2upper	= charset2upper,
> >  };
> 
> iocharset=default was gone with this (user visible) change? (nobody
> notice it though)
> 
> > -/* Returns a simple default translation table */
> > +/* Returns a default translation table */
> >  struct nls_table *load_nls_default(void)
> >  {
> >  	struct nls_table *default_nls;
> > @@ -537,9 +419,22 @@ struct nls_table *load_nls_default(void)
> >  	if (default_nls != NULL)
> >  		return default_nls;
> >  	else
> > -		return &default_table;
> > +		return &iso8859_1_table;
> > +}
> > +
> > +static int __init init_nls(void)
> > +{
> > +	return register_nls(&iso8859_1_table);
> >  }
> >  
> > +static void __exit exit_nls(void)
> > +{
> > +	unregister_nls(&iso8859_1_table);
> > +}
> > +
> > +module_init(init_nls)
> > +module_exit(exit_nls)
> 
> [...]
> 
> Do we need to merge nls_iso8859-1.c to nls_base.c?
> 
> 	obj-$(CONFIG_NLS)		+= nls_iso8859-1.o nls_base.o
> 
> Something like this (untested), maybe cleaner.
> 
> Thanks.
> -- 
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
I will look at it.
     prev parent reply	other threads:[~2023-02-04 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 14:42 [RFC PATCH 0/3] fs: nls: Simplification of ASCII and ISO-8859-1 Pali Rohár
2022-12-26 14:42 ` [RFC PATCH 1/3] nls: Simplify ASCII implementation Pali Rohár
2022-12-26 14:43 ` [RFC PATCH 2/3] nls: Simplify ISO-8859-1 implementation Pali Rohár
2022-12-26 14:43 ` [RFC PATCH 3/3] nls: Replace default nls table by correct iso8859-1 table Pali Rohár
2023-01-10  7:52   ` kernel test robot
2023-01-10  9:23   ` OGAWA Hirofumi
2023-02-04 10:58     ` Pali Rohár [this message]
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=20230204105807.jdd2rrrzf37hns6h@pali \
    --to=pali@kernel.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).