From: "Darrick J. Wong" <djwong@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <kees@kernel.org>, Carlos Maiolino <cem@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
linux-xfs@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v4 3/3] xfs: adjust handling of a few numerical mount options
Date: Tue, 20 Jan 2026 14:55:31 -0800 [thread overview]
Message-ID: <20260120225531.GZ15551@frogsfrogsfrogs> (raw)
In-Reply-To: <aW_4bxkLe4-g9teu@smile.fi.intel.com>
On Tue, Jan 20, 2026 at 11:49:35PM +0200, Andy Shevchenko wrote:
> On Tue, Jan 20, 2026 at 07:57:50PM +0300, Dmitry Antipov wrote:
> > On Tue, 2026-01-20 at 16:59 +0200, Andy Shevchenko wrote:
> >
> > > With all this, I do not see the point of having a new API.
> > > Also, where are the test cases for it?
>
> > If there is no point, why worrying about tests?
>
> I don't know yet if there is a point or not, I provided my view.
> I think you know better than me the code in question. It might
> be that I'm mistaken, and if so the good justification in the
> (currently absent) cover letter may well help with that.
>
> > Also, do you always communicate with the people
> > just like they're your (well-) paid personnel?
>
> What do you mean? Test cases is the requirement for the new APIs
> added to the lib/. It's really should be regular practice for
> the code development independently on the project. If you think
> frustrated by this, I can tell you that I was more than once in
> the past in the same situation until I learnt it very well and
> now when I submit anything to the lib I always add test cases.
Yes. Common code needs to have a rigorous self test suite, because I
see no point in replacing inadequately tested bespoke parsing code with
inadequately tested common parsing code.
--D
> --
> With Best Regards,
> Andy Shevchenko
>
>
>
next prev parent reply other threads:[~2026-01-20 22:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 16:52 [PATCH v3 1/2] lib: introduce simple error-checking wrapper for memparse() Dmitry Antipov
2026-01-08 16:52 ` [PATCH v3 2/2] xfs: adjust handling of a few numerical mount options Dmitry Antipov
2026-01-08 17:06 ` [PATCH v3 1/2] lib: introduce simple error-checking wrapper for memparse() Kees Cook
2026-01-08 17:42 ` Andrew Morton
2026-01-08 17:55 ` Kees Cook
2026-01-09 12:53 ` Carlos Maiolino
2026-01-08 20:05 ` Andy Shevchenko
2026-01-09 11:41 ` Dmitry Antipov
2026-01-09 17:09 ` Andy Shevchenko
2026-01-09 17:11 ` Andy Shevchenko
2026-01-11 0:01 ` Andrew Morton
2026-01-08 20:10 ` Andy Shevchenko
2026-01-09 11:05 ` Dmitry Antipov
2026-01-09 11:18 ` Andy Shevchenko
2026-01-20 0:06 ` Andrew Morton
2026-01-20 14:12 ` [PATCH v4 1/3] " Dmitry Antipov
2026-01-20 14:12 ` [PATCH v4 2/3] lib: fix a few comments to match kernel-doc -Wreturn style Dmitry Antipov
2026-01-20 14:47 ` Andy Shevchenko
2026-01-20 14:12 ` [PATCH v4 3/3] xfs: adjust handling of a few numerical mount options Dmitry Antipov
2026-01-20 14:59 ` Andy Shevchenko
2026-01-20 16:57 ` Dmitry Antipov
2026-01-20 21:49 ` Andy Shevchenko
2026-01-20 22:55 ` Darrick J. Wong [this message]
2026-01-21 5:21 ` Dmitry Antipov
2026-01-21 13:25 ` Andy Shevchenko
2026-01-20 14:45 ` [PATCH v4 1/3] lib: introduce simple error-checking wrapper for memparse() Andy Shevchenko
2026-01-20 14:46 ` Andy Shevchenko
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=20260120225531.GZ15551@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@intel.com \
--cc=cem@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=hch@infradead.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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.