From: R Sundar <prosunofficial@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Kees Cook <kees@kernel.org>, Andy Shevchenko <andy@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH linux-next] lib/string_choices: Add str_locked_unlocked()/str_unlocked_locked() helper
Date: Sat, 16 Nov 2024 09:18:21 +0530 [thread overview]
Message-ID: <2a5500a5-c1b6-4c5c-bf37-4cfeda5a9e1e@gmail.com> (raw)
In-Reply-To: <CAHp75VdD1KYh9KJWHwhxkXy-+jfh_o=Rn05AtL4QBb0HC-oz6g@mail.gmail.com>
On 16/11/24 01:16, Andy Shevchenko wrote:
> On Fri, Nov 15, 2024 at 9:44 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
>> On Fri, Nov 15, 2024 at 4:47 PM R Sundar <prosunofficial@gmail.com> wrote:
>
> ...
>
>>> --- a/include/linux/string_choices.h
>>> +++ b/include/linux/string_choices.h
>>> @@ -82,4 +82,10 @@ static inline const char *str_plural(size_t num)
>>> return num == 1 ? "" : "s";
>>> }
>>>
>>> +static inline const char *str_locked_unlocked(bool v)
>>> +{
>>> + return v ? "locked" : "unlocked";
>>> +}
>>> +#define str_unlocked_locked(v) str_locked_unlocked(!(v))
>>
>> The rest is sorted (okay, read_write() seems to be misplaced, fix that
>> in a separate change if you wish), please keep it that way (I believe
>> it should go before on_off).
>
Hi,
Thanks for the Review and Comments provided.
Please correct me, If I am wrong.
The function name should be in sorted order means, str_read_write()
will go after str_on_off().
For example, the sorted order of function will be like:
str_on_off()
str_plural()
str_read_write()
> Oh, I looked in v6.11 code, in v6.12 there are a couple of more
> misplacements. Can you fix them all, please?
>
Sure, Will sort it and send as seperate patch.
Thanks,
Sundar
next prev parent reply other threads:[~2024-11-16 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 14:46 [PATCH linux-next] lib/string_choices: Add str_locked_unlocked()/str_unlocked_locked() helper R Sundar
2024-11-15 19:44 ` Andy Shevchenko
2024-11-15 19:46 ` Andy Shevchenko
2024-11-16 3:48 ` R Sundar [this message]
2024-11-17 20:03 ` Andy Shevchenko
2024-11-18 3:10 ` R Sundar
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=2a5500a5-c1b6-4c5c-bf37-4cfeda5a9e1e@gmail.com \
--to=prosunofficial@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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