From: Simon Horman <simon.horman@corigine.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Xin Long <lucien.xin@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
dev@openvswitch.org, tipc-discussion@lists.sourceforge.net,
Andy Shevchenko <andy@kernel.org>, Jon Maloy <jmaloy@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Ying Xue <ying.xue@windriver.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [ovs-dev] [PATCH v1 3/3] openvswitch: Use string_is_valid() helper
Date: Sat, 4 Feb 2023 14:26:44 +0100 [thread overview]
Message-ID: <Y95dFGwEDyFx7m2R@corigine.com> (raw)
In-Reply-To: <20230203140501.67659-3-andriy.shevchenko@linux.intel.com>
On Fri, Feb 03, 2023 at 04:05:01PM +0200, Andy Shevchenko wrote:
> Use string_is_valid() helper instead of cpecific memchr() call.
> This shows better the intention of the call.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
For networking patches, the target tree, in this case net-next, should
appear in the patch subject:
[PATCH v1 net-next 3/3] openvswitch: Use string_is_valid()
That notwithstanding,
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-02-04 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 14:04 [PATCH v1 1/3] string_helpers: Move string_is_valid() to the header Andy Shevchenko
2023-02-03 14:05 ` [PATCH v1 2/3] genetlink: Use string_is_valid() helper Andy Shevchenko
2023-02-04 13:25 ` [ovs-dev] " Simon Horman
2023-02-03 14:05 ` [PATCH v1 3/3] openvswitch: " Andy Shevchenko
2023-02-04 13:26 ` Simon Horman [this message]
2023-02-04 13:25 ` [ovs-dev] [PATCH v1 1/3] string_helpers: Move string_is_valid() to the header Simon Horman
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=Y95dFGwEDyFx7m2R@corigine.com \
--to=simon.horman@corigine.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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