linux-kernel - Re: [PATCH][next] bcachefs: Fix a handful of spelling mistakes in various messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230912150414.p3fx5ryd77e2ju43@moria.home.lan>
Date:   Tue, 12 Sep 2023 11:04:14 -0400
From:   Kent Overstreet <kent.overstreet@...ux.dev>
To:     "Colin King (gmail)" <colin.i.king@...il.com>
Cc:     Brian Foster <bfoster@...hat.com>, linux-bcachefs@...r.kernel.org,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] bcachefs: Fix a handful of spelling mistakes in
 various messages

On Tue, Sep 12, 2023 at 04:00:23PM +0100, Colin King (gmail) wrote:
> On 12/09/2023 14:51, Brian Foster wrote:
> > On Tue, Sep 12, 2023 at 09:25:27AM +0100, Colin Ian King wrote:
> > > There are several spelling mistakes in error messages. Fix these.
> > > 
> > > Signed-off-by: Colin Ian King <colin.i.king@...il.com>
> > > ---
> > >   fs/bcachefs/alloc_background.c | 2 +-
> > >   fs/bcachefs/backpointers.c     | 2 +-
> > >   fs/bcachefs/btree_iter.c       | 2 +-
> > >   fs/bcachefs/fsck.c             | 2 +-
> > >   fs/bcachefs/recovery.c         | 2 +-
> > >   fs/bcachefs/snapshot.c         | 2 +-
> > >   fs/bcachefs/super-io.c         | 2 +-
> > >   7 files changed, 7 insertions(+), 7 deletions(-)
> > > 
> > > diff --git a/fs/bcachefs/alloc_background.c b/fs/bcachefs/alloc_background.c
> > > index 540d94c0cceb..dd9f3cbace1e 100644
> > > --- a/fs/bcachefs/alloc_background.c
> > > +++ b/fs/bcachefs/alloc_background.c
> > > @@ -1247,7 +1247,7 @@ static noinline_for_stack int __bch2_check_discard_freespace_key(struct btree_tr
> > >   		return ret;
> > >   	if (fsck_err_on(!bch2_dev_bucket_exists(c, pos), c,
> > > -			"entry in %s btree for nonexistant dev:bucket %llu:%llu",
> > > +			"entry in %s btree for non-existent dev:bucket %llu:%llu",
> > 
> > "nonexistent" doesn't necessarily need to be hyphenated, right?
> 
> either way is valid, but some folk prefer the hyphenated version as it's
> apparently easier to scan.

Let's stick with the non hyphenated.