From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, christophe.jaillet@wanadoo.fr,
David.Laight@aculab.com, ddiss@suse.de, geert@linux-m68k.org,
rdunlap@infradead.org
Subject: Re: [PATCH v4 0/4] kstrtox: introduce memparse_safe()
Date: Sat, 6 Jan 2024 16:35:11 +0200 [thread overview]
Message-ID: <ZZllH1Aw_XKw1EW5@smile.fi.intel.com> (raw)
In-Reply-To: <cover.1704422015.git.wqu@suse.com>
On Fri, Jan 05, 2024 at 01:04:58PM +1030, Qu Wenruo wrote:
> [CHANGELOG]
> v4:
> - Extra test cases for supported but not enabled suffixes
>
> - Comments update for memparse_safe() function
Same comment is applied as per v3.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-01-06 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 2:34 [PATCH v4 0/4] kstrtox: introduce memparse_safe() Qu Wenruo
2024-01-05 2:34 ` [PATCH v4 1/4] kstrtox: always skip the leading "0x" even if no more valid chars Qu Wenruo
2024-01-05 2:35 ` [PATCH v4 2/4] kstrtox: introduce a safer version of memparse() Qu Wenruo
2024-01-15 4:27 ` Randy Dunlap
2024-01-15 5:27 ` Qu Wenruo
2024-01-18 17:52 ` Randy Dunlap
2024-01-05 2:35 ` [PATCH v4 3/4] kstrtox: add unit tests for memparse_safe() Qu Wenruo
2024-01-05 2:35 ` [PATCH v4 4/4] btrfs: migrate to the newer memparse_safe() helper Qu Wenruo
2024-01-05 19:04 ` David Sterba
2024-01-06 14:35 ` Andy Shevchenko [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=ZZllH1Aw_XKw1EW5@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=ddiss@suse.de \
--cc=geert@linux-m68k.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=wqu@suse.com \
/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