netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: sam@mendozajonas.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net/ncsi: Use str_up_down to simplify the code
Date: Tue, 27 Aug 2024 09:52:48 +0100	[thread overview]
Message-ID: <20240827085248.GB1368797@kernel.org> (raw)
In-Reply-To: <20240827025246.963115-1-lihongbo22@huawei.com>

On Tue, Aug 27, 2024 at 10:52:44AM +0800, Hongbo Li wrote:
> In commit a98ae7f045b2, str_up_down() helper is introduced to
> return "up" or "down" string literal, so we can use it to
> simplify the code and fix the coccinelle warning.
> 
> v2:
>  - change subject into net-next
> 
> v1: https://lore.kernel.org/netdev/20240823162144.GW2164@kernel.org/T/

Thanks, but another problem I raised wrt to v1 still stands.
There is a dependency of this patch that is not present in net-next:
commit a98ae7f045b2 ("lib/string_choices: Add str_up_down() helper").

So I think you will need to repost once that commit has
made it into net-next.

-- 
pw-bot: cr

  parent reply	other threads:[~2024-08-27  8:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  2:52 [PATCH net-next v2 0/2] net/ncsi: Use str_up_down to simplify the code Hongbo Li
2024-08-27  2:52 ` [PATCH net-next v2 1/2] " Hongbo Li
2024-08-27  7:04   ` Michal Swiatkowski
2024-08-27 16:23   ` kernel test robot
2024-08-27 17:34   ` kernel test robot
2024-08-27  2:52 ` [PATCH net-next v2 2/2] " Hongbo Li
2024-08-27 18:26   ` kernel test robot
2024-08-27  8:52 ` Simon Horman [this message]
2024-08-27  9:11   ` [PATCH net-next v2 0/2] " Hongbo Li

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=20240827085248.GB1368797@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sam@mendozajonas.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;
as well as URLs for NNTP newsgroup(s).