From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Hans de Goede <hdegoede@redhat.com>, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1 3/3] lib/string_helpers: Split out string_choices.h
Date: Wed, 30 Nov 2022 13:51:45 +0200 [thread overview]
Message-ID: <Y4dD0QaMO64jBnWn@smile.fi.intel.com> (raw)
In-Reply-To: <20221130115022.68956-3-andriy.shevchenko@linux.intel.com>
On Wed, Nov 30, 2022 at 01:50:22PM +0200, Andy Shevchenko wrote:
> Some users may only need the string choice APIs. Split
> the respective header, i.e. string_choices.h. Include
> it in the string_helpers.h.
This one can be skipped for now, can be considered just an idea.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-30 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 11:50 [PATCH v1 1/3] lib/string_helpers: Add missing header files to MAINTAINERS database Andy Shevchenko
2022-11-30 11:50 ` [PATCH v1 2/3] lib/string_helpers: Add str_high_low() helper Andy Shevchenko
2022-11-30 11:50 ` [PATCH v1 3/3] lib/string_helpers: Split out string_choices.h Andy Shevchenko
2022-11-30 11:51 ` 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=Y4dD0QaMO64jBnWn@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox