From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Mohammad Heib <mheib@redhat.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next] i40e: delete a stray tab
Date: Fri, 21 Nov 2025 17:23:01 -0800 [thread overview]
Message-ID: <20251121172301.3f488693@kernel.org> (raw)
In-Reply-To: <d396e86c-e466-4630-8b1f-7f5b640d88a5@intel.com>
On Fri, 21 Nov 2025 14:35:07 -0800 Tony Nguyen wrote:
> On 11/21/2025 5:35 AM, Dan Carpenter wrote:
> > This return statement is indented one tab too far. Delete a tab.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
>
> netdev maintainers. This seems straightforward enough, did you want to
> take this directly?
Will, do!
> Reviewed-by: Tony Nguyen <anthony.l.nguyen@intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Mohammad Heib <mheib@redhat.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH net-next] i40e: delete a stray tab
Date: Fri, 21 Nov 2025 17:23:01 -0800 [thread overview]
Message-ID: <20251121172301.3f488693@kernel.org> (raw)
In-Reply-To: <d396e86c-e466-4630-8b1f-7f5b640d88a5@intel.com>
On Fri, 21 Nov 2025 14:35:07 -0800 Tony Nguyen wrote:
> On 11/21/2025 5:35 AM, Dan Carpenter wrote:
> > This return statement is indented one tab too far. Delete a tab.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
>
> netdev maintainers. This seems straightforward enough, did you want to
> take this directly?
Will, do!
> Reviewed-by: Tony Nguyen <anthony.l.nguyen@intel.com>
next prev parent reply other threads:[~2025-11-22 1:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 13:35 [Intel-wired-lan] [PATCH net-next] i40e: delete a stray tab Dan Carpenter
2025-11-21 13:35 ` Dan Carpenter
2025-11-21 22:35 ` [Intel-wired-lan] " Tony Nguyen
2025-11-21 22:35 ` Tony Nguyen
2025-11-22 1:23 ` Jakub Kicinski [this message]
2025-11-22 1:23 ` Jakub Kicinski
2025-11-24 7:07 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-24 7:07 ` Loktionov, Aleksandr
2025-11-25 3:10 ` patchwork-bot+netdevbpf
2025-11-25 3:10 ` 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=20251121172301.3f488693@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mheib@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.