From: Jakub Kicinski <kuba@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Julia Lawall <Julia.Lawall@inria.fr>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Justin Chen <justin.chen@broadcom.com>,
Paolo Abeni <pabeni@redhat.com>,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, cocci@inria.fr,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: bcmasp: Use common error handling code in bcmasp_probe()
Date: Mon, 6 Nov 2023 14:58:06 -0800 [thread overview]
Message-ID: <20231106145806.669875f4@kernel.org> (raw)
In-Reply-To: <0b2972cb-03b2-40c7-a728-6ebe2512637f@web.de>
On Sun, 5 Nov 2023 17:33:46 +0100 Markus Elfring wrote:
> Add a jump target so that a bit of exception handling can be better
> reused at the end of this function.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
> drivers/net/ethernet/broadcom/asp2/bcmasp.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
The diffstat proves otherwise.
Please don't send such patches to networking.
next prev parent reply other threads:[~2023-11-06 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 16:33 [PATCH] net: bcmasp: Use common error handling code in bcmasp_probe() Markus Elfring
2023-11-06 10:02 ` Wojciech Drewek
2023-11-06 13:55 ` Markus Elfring
2023-11-06 14:24 ` Wojciech Drewek
2023-11-06 22:58 ` Jakub Kicinski [this message]
2023-11-07 6:38 ` Markus Elfring
2023-11-07 18:48 ` Justin Chen
2023-11-08 17:46 ` Florian Fainelli
2023-11-15 9:10 ` [PATCH v2] " Markus Elfring
2023-11-16 19:05 ` Justin Chen
2023-11-16 20:24 ` Markus Elfring
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=20231106145806.669875f4@kernel.org \
--to=kuba@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=cocci@inria.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).