From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: sam@mendozajonas.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] net/ncsi: Use str_up_down to simplify the code
Date: Tue, 27 Aug 2024 09:04:28 +0200 [thread overview]
Message-ID: <Zs16fFk7sDIhcMP8@mev-dev.igk.intel.com> (raw)
In-Reply-To: <20240827025246.963115-2-lihongbo22@huawei.com>
On Tue, Aug 27, 2024 at 10:52:45AM +0800, Hongbo Li wrote:
> As str_up_down is the common helper to reback "up/down"
> string, we can replace the target with it to simplify
> the code and fix the coccinelle warning.
>
> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
> ---
> net/ncsi/ncsi-manage.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ncsi/ncsi-manage.c b/net/ncsi/ncsi-manage.c
> index 5ecf611c8820..13b4d393fb2d 100644
> --- a/net/ncsi/ncsi-manage.c
> +++ b/net/ncsi/ncsi-manage.c
> @@ -1281,7 +1281,7 @@ static int ncsi_choose_active_channel(struct ncsi_dev_priv *ndp)
> netdev_dbg(ndp->ndev.dev,
> "NCSI: Channel %u added to queue (link %s)\n",
> nc->id,
> - ncm->data[2] & 0x1 ? "up" : "down");
> + str_up_down(ncm->data[2] & 0x1));
Are you basing the commit on sth else than net-next? I can't see such
helper in the repo.
> }
>
> spin_unlock_irqrestore(&nc->lock, cflags);
> --
> 2.34.1
>
You have the same commit message in both patches, they can be merged
into one I think.
Thanks,
Michal
next prev parent reply other threads:[~2024-08-27 7:06 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 [this message]
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 ` [PATCH net-next v2 0/2] " Simon Horman
2024-08-27 9:11 ` 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=Zs16fFk7sDIhcMP8@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.