From: Martin Habets <habetsm.xilinx@gmail.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: kuba@kernel.org, davem@davemloft.net, ecree.xilinx@gmail.com,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] sfc: clean up some inconsistent indentings
Date: Mon, 20 Feb 2023 08:35:37 +0000 [thread overview]
Message-ID: <Y/Mw2UZ7KRF8iWfD@gmail.com> (raw)
In-Reply-To: <20230220065958.52941-1-yang.lee@linux.alibaba.com>
Please fix the subject to use [PATCH net-next].
On Mon, Feb 20, 2023 at 02:59:58PM +0800, Yang Li wrote:
> Fix some indentngs and remove the warning below:
> drivers/net/ethernet/sfc/mae.c:657 efx_mae_enumerate_mports() warn: inconsistent indenting
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=4117
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Acked-by: Martin Habets <habetsm.xilinx@gmail.com>
> ---
> drivers/net/ethernet/sfc/mae.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/sfc/mae.c b/drivers/net/ethernet/sfc/mae.c
> index 6321fd393fc3..2d32abe5f478 100644
> --- a/drivers/net/ethernet/sfc/mae.c
> +++ b/drivers/net/ethernet/sfc/mae.c
> @@ -654,8 +654,8 @@ int efx_mae_enumerate_mports(struct efx_nic *efx)
> MAE_MPORT_DESC_VNIC_FUNCTION_INTERFACE);
> d->pf_idx = MCDI_STRUCT_WORD(desc,
> MAE_MPORT_DESC_VNIC_FUNCTION_PF_IDX);
> - d->vf_idx = MCDI_STRUCT_WORD(desc,
> - MAE_MPORT_DESC_VNIC_FUNCTION_VF_IDX);
> + d->vf_idx = MCDI_STRUCT_WORD(desc,
> + MAE_MPORT_DESC_VNIC_FUNCTION_VF_IDX);
> break;
> default:
> /* Unknown mport_type, just accept it */
> --
> 2.20.1.7.g153144c
next prev parent reply other threads:[~2023-02-20 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 6:59 [PATCH -next] sfc: clean up some inconsistent indentings Yang Li
2023-02-20 8:35 ` Martin Habets [this message]
2023-02-21 0:50 ` patchwork-bot+netdevbpf
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=Y/Mw2UZ7KRF8iWfD@gmail.com \
--to=habetsm.xilinx@gmail.com \
--cc=abaci@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yang.lee@linux.alibaba.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).