From: Heiner Kallweit <hkallweit1@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/2] lib: string: add strreplace_nonalnum
Date: Sun, 3 Mar 2019 19:36:31 +0100 [thread overview]
Message-ID: <78b4ac4c-009f-7968-13ec-a0d92d941a87@gmail.com> (raw)
In-Reply-To: <d92b7418-09bb-15bc-85f8-508f992ed2c6@gmail.com>
On 03.03.2019 18:19, Heiner Kallweit wrote:
> Add a new function strreplace_nonalnum that replaces all
> non-alphanumeric characters. Such functionality is needed e.g. when a
> string is supposed to be used in a file name. If '\0' is given as new
> character then non-alphanumeric characters are cut.
>
> There doesn't seem to be a maintainer or mailing list for lib/string.c
> Therefore I hope it's ok to submit this through the netdev tree.
>
> Heiner Kallweit (2):
> lib: string: add strreplace_nonalnum
> net: phy: aquantia: use new function strreplace_nonalnum
>
> drivers/net/phy/aquantia_hwmon.c | 10 +---------
> include/linux/string.h | 1 +
> lib/string.c | 27 +++++++++++++++++++++++++++
> 3 files changed, 29 insertions(+), 9 deletions(-)
>
Greg still has some concerns, let's see what the outcome of this
discussion is.
https://lkml.org/lkml/2019/3/3/151
next prev parent reply other threads:[~2019-03-03 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 17:19 [PATCH net-next 0/2] lib: string: add strreplace_nonalnum Heiner Kallweit
2019-03-03 17:20 ` [PATCH net-next 1/2] " Heiner Kallweit
2019-03-03 17:21 ` [PATCH net-next 2/2] net: phy: aquantia: use new function strreplace_nonalnum Heiner Kallweit
2019-03-03 17:31 ` Andrew Lunn
2019-03-03 17:41 ` Heiner Kallweit
2019-03-03 17:34 ` [PATCH net-next 0/2] lib: string: add strreplace_nonalnum Andrew Lunn
2019-03-03 17:39 ` Heiner Kallweit
2019-03-03 18:36 ` Heiner Kallweit [this message]
2019-03-04 18:54 ` Heiner Kallweit
2019-03-04 19:22 ` David Miller
2019-03-04 19:27 ` Heiner Kallweit
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=78b4ac4c-009f-7968-13ec-a0d92d941a87@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).