From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Josh Law <objecting@objecting.org>
Cc: david@davidgow.net, note351@hotmail.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
rostedt@goodmis.org
Subject: Re: [PATCH] lib/glob: add more KUnit tests for glob
Date: Sat, 4 Apr 2026 00:10:55 +0800 [thread overview]
Message-ID: <ac_mj_YUIdyrv9Mz@google.com> (raw)
In-Reply-To: <19d540a3afb.4e80747a170670.7200857965755638934@objecting.org>
On Fri, Apr 03, 2026 at 04:50:49PM +0100, Josh Law wrote:
> ---- On Fri, 03 Apr 2026 16:49:10 +0100 visitorckw@gmail.com wrote ----
>
>
> > Hi Josh,
> >
> > On Fri, Apr 03, 2026 at 03:28:53PM +0000, Josh Law wrote:
> > > Since there isnt much tests for lib/glob.c, lets go ahead and add some more
> > tests
> >
> > checkpatch.pl generates the following warnings:
> >
> > WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit
> > description?)
> > #60:
> > Since there isnt much tests for lib/glob.c, lets go ahead and add some more
> > tests
> >
> > WARNING: 'isnt' may be misspelled - perhaps 'isn't'?
> > #60:
> > Since there isnt much tests for lib/glob.c, lets go ahead and add some more
> > tests
> > ^^^^
> >
> > total: 0 errors, 2 warnings, 31 lines checked
> >
> > I have mentioned this to you multiple times in the past: please always
> > run checkpatch.pl to check your patches before sending them.
> >
> > Regards,
> > Kuan-Wei
> Hi Kuan, it was genuinely my mistake. I forgot to run check patch before sending it over. And this happened. I'll give it a bit before sending over a V2 fixing these issues :)
Additionally, I believe many different people have already pointed out
the word-wrapping issues in your replies. Some developers are even
getting frustrated because of the repeated reminders. You have promised
to fix this, yet every time you send a new email, the exact same
problem persists.
I would suggest that you figure out how to completely resolve this
issue before attempting to submit new patches. Furthermore, you
recently mentioned that you were going to take a break for a while, but
less than a few days later, I am already receiving another patch from
you.
Regards,
Kuan-Wei
> >
> > >
> > > Signed-off-by: Josh Law
> >
> > > ---
> > > lib/tests/glob_kunit.c | 25 +++++++++++++++++++++++++
> > > 1 file changed, 25 insertions(+)
> > >
> > > diff --git a/lib/tests/glob_kunit.c b/lib/tests/glob_kunit.c
> > > index 362b1eda8e5b..73d4f72fa824 100644
> > > --- a/lib/tests/glob_kunit.c
> > > +++ b/lib/tests/glob_kunit.c
> > > @@ -90,6 +90,31 @@ static const struct glob_test_case glob_test_cases[] = {
> > > { .pat = "*abcd*abcdef*", .str = "abcabcdabcdeabcdefg", .expected = true
> > },
> > > { .pat = "*abcd*", .str = "abcabcabcabcefg", .expected = false },
> > > { .pat = "*ab*cd*", .str = "abcabcabcabcefg", .expected = false },
> > > + /* backslash escaping */
> > > + { .pat = "\\a", .str = "a", .expected = true },
> > > + { .pat = "\\a", .str = "\\a", .expected = false },
> > > + { .pat = "\\*", .str = "*", .expected = true },
> > > + { .pat = "\\*", .str = "a", .expected = false },
> > > + { .pat = "\\?", .str = "?", .expected = true },
> > > + { .pat = "\\?", .str = "a", .expected = false },
> > > + { .pat = "\\[a]", .str = "[a]", .expected = true },
> > > + { .pat = "\\\\", .str = "\\", .expected = true },
> > > + { .pat = "a\\*b", .str = "a*b", .expected = true },
> > > + { .pat = "a\\*b", .str = "aXb", .expected = false },
> > > + /* trailing backslash */
> > > + { .pat = "a\\", .str = "a", .expected = true },
> > > + { .pat = "\\", .str = "", .expected = true },
> > > + /* backwards ranges */
> > > + { .pat = "[z-a]", .str = "m", .expected = false },
> > > + { .pat = "[!z-a]", .str = "m", .expected = true },
> > > + /* high-bit characters */
> > > + { .pat = "\xc0", .str = "\xc0", .expected = true },
> > > + { .pat = "\xc0", .str = "\x80", .expected = false },
> > > + { .pat = "[\x80-\xff]", .str = "\xc0", .expected = true },
> > > + { .pat = "[\x80-\xff]", .str = "\x7f", .expected = false },
> > > + /* unclosed bracket as literal */
> > > + { .pat = "[abc", .str = "[abc", .expected = true },
> > > + { .pat = "[abc", .str = "a", .expected = false },
> > > };
> > >
> > > static void glob_case_to_desc(const struct glob_test_case *t, char *desc)
> > > --
> > > 2.34.1
> > >
>
prev parent reply other threads:[~2026-04-03 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 15:28 [PATCH] lib/glob: add more KUnit tests for glob Josh Law
2026-04-03 15:49 ` Kuan-Wei Chiu
2026-04-03 15:50 ` Josh Law
2026-04-03 16:10 ` Kuan-Wei Chiu [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=ac_mj_YUIdyrv9Mz@google.com \
--to=visitorckw@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@davidgow.net \
--cc=linux-kernel@vger.kernel.org \
--cc=note351@hotmail.com \
--cc=objecting@objecting.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox