From: Chris Brannon <chris@the-brannons.com>
To: Markus Mayer <mmayer@broadcom.com>
Cc: William Hubbs <w.d.hubbs@gmail.com>,
Kirk Reiser <kirk@reisers.ca>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
speakup@linux-speakup.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/7] staging: speakup: replace spk_strlwr() with strlcpytolower()
Date: Fri, 22 Jul 2016 16:53:24 -0700 [thread overview]
Message-ID: <87lh0tp6vf.fsf@mushroom.localdomain> (raw)
In-Reply-To: <1469230269-1644-5-git-send-email-mmayer@broadcom.com> (Markus Mayer's message of "Fri, 22 Jul 2016 16:31:06 -0700")
Markus Mayer <mmayer@broadcom.com> writes:
> After introducing generic strltolower() and strtolower(), spk_strlwr()
> is no longer needed.
>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Acked-by: Chris Brannon <chris@the-brannons.com>
Haven't looked at much kernel code in a while, but this looks good.
-- Chris
next prev parent reply other threads:[~2016-07-23 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 23:31 [PATCH v4 0/7] lib: string: add functions to case-convert strings Markus Mayer
2016-07-22 23:31 ` [PATCH v4 1/7] " Markus Mayer
2016-07-22 23:31 ` [PATCH v4 2/7] drm/nouveau/core: make use of new strlcpytolower() function Markus Mayer
2016-07-22 23:31 ` [PATCH v4 3/7] ACPI / device_sysfs: make use of new strtolower() function Markus Mayer
2016-07-22 23:31 ` [PATCH v4 4/7] staging: speakup: replace spk_strlwr() with strlcpytolower() Markus Mayer
2016-07-22 23:53 ` Chris Brannon [this message]
2016-07-22 23:31 ` [PATCH v4 5/7] iscsi-target: replace iscsi_initiatorname_tolower() with strtolower() Markus Mayer
2016-07-22 23:31 ` [PATCH v4 6/7] drm/nouveau/fifo/gk104: make use of new strcpytoupper() function Markus Mayer
2016-07-22 23:31 ` [PATCH v4 7/7] power_supply: " Markus Mayer
2016-07-23 0:00 ` Sebastian Reichel
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=87lh0tp6vf.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.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
all inboxes | Powered by JetHome®