All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Wei Wang <weibunny@meta.com>
Cc: Daniel Zahka <daniel.zahka@gmail.com>,
	Wei Wang <weibunny.kernel@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Wei Wang <weibunny@fb.com>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH net] psp: use unrcu_pointer() for the cmpxchg() on netdev psp_dev
Date: Fri, 14 Aug 2026 10:07:32 -0700	[thread overview]
Message-ID: <20260814100732.542308e1@kernel.org> (raw)
In-Reply-To: <CADe0Y=sQ0e=snxJBd6kBz08eYR4BrX_9Xbr=XEHGVcXzybfQow@mail.gmail.com>

On Thu, 13 Aug 2026 13:37:23 -0700 Wei Wang wrote:
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Closes: https://lore.kernel.org/oe-kbuild-all/202608080910.l9KvOH7O-lkp@intel.com/
> > > Signed-off-by: Wei Wang <weibunny@fb.com>  
> > Commits targeting the net tree need a fixes tag.  
> 
> This is a sparse warning fix, my understanding is that it's not a
> functional fix and therefore should not use a Fixes tag. Please let me
> know if my understanding is wrong.

I mentioned "no Fixes tag needed" in internal review, I should have 
been more clear that this implies net-next, sorry. 

No need to repost - we'll route it to net-next when applying.

  reply	other threads:[~2026-08-14 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 19:34 [PATCH net] psp: use unrcu_pointer() for the cmpxchg() on netdev psp_dev Wei Wang
2026-08-13 19:57 ` Daniel Zahka
2026-08-13 20:37   ` Wei Wang
2026-08-14 17:07     ` Jakub Kicinski [this message]
2026-08-14 17:27       ` Wei Wang

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=20260814100732.542308e1@kernel.org \
    --to=kuba@kernel.org \
    --cc=daniel.zahka@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=weibunny.kernel@gmail.com \
    --cc=weibunny@fb.com \
    --cc=weibunny@meta.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.