All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: netdev@vger.kernel.org, "Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Julia Lawall" <julia.lawall@inria.fr>,
	"MD Danish Anwar" <danishanwar@ti.com>,
	"Michael Grzeschik" <mgr@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Vadim Fedorenko" <vadim.fedorenko@linux.dev>,
	"Yibo Dong" <dong100@mucse.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	"Dan Carpenter" <error27@gmail.com>
Subject: Re: [PATCH v3 net-next] net: rnpgbe: Delete a null pointer check in rnpgbe_rm_adapter()
Date: Wed, 22 Jul 2026 12:40:41 -0700	[thread overview]
Message-ID: <20260722124041.126a7aa2@kernel.org> (raw)
In-Reply-To: <7a9ea765-2c75-4a16-aaf9-510f2450beb3@web.de>

On Fri, 17 Jul 2026 10:38:32 +0200 Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Fri, 17 Jul 2026 10:20:15 +0200
> 
> The check for the pointer “mucse” was identified as redundant because
> the relevant address information was preserved according to calls of
> the functions “pci_set_drvdata” and “pci_get_drvdata”.
> Thus remove it.
> 
> This issue was detected by using the Coccinelle software.

pointless churn, please don't waste our time

      parent reply	other threads:[~2026-07-22 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  8:38 [PATCH v3 net-next] net: rnpgbe: Delete a null pointer check in rnpgbe_rm_adapter() Markus Elfring
2026-07-17 16:07 ` Andrew Lunn
2026-07-22 19:40 ` Jakub Kicinski [this message]

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=20260722124041.126a7aa2@kernel.org \
    --to=kuba@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=andrew+netdev@lunn.ch \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=dong100@mucse.com \
    --cc=edumazet@google.com \
    --cc=error27@gmail.com \
    --cc=julia.lawall@inria.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgr@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=u.kleine-koenig@baylibre.com \
    --cc=vadim.fedorenko@linux.dev \
    /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.