netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Johan Korsnes <johan.korsnes@gmail.com>
Cc: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	netdev@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH] net: au1000_eth: Mark au1000_ReleaseDB() static
Date: Tue, 25 Mar 2025 02:45:02 -0700	[thread overview]
Message-ID: <20250325024502.70a84c3f@kernel.org> (raw)
In-Reply-To: <16fd5d51-fc2e-453c-9e81-c2530e4d3ea7@gmail.com>

On Mon, 24 Mar 2025 09:21:29 +0100 Johan Korsnes wrote:
> > Thanks for fixing it
> > Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> > 
> > You didn't specify the tree (net vs net-next in [PATCH ...]). If you
> > want it to go to net you will need fixes tag, if to net-next it is fine.  
> 
> Thank you for the review. I don't mind adding fixes tags and re-submit,
> but would that be preferred in this case? Or will it just be noise for
> the maintainers?

Just noise.

Michal, when PW bot guesses the tree correctly there is no need to flag
the problem to the contributor. The tree designation makes our life
easier but not enough to deal with reposts.

  reply	other threads:[~2025-03-25  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-23 19:04 [PATCH] net: au1000_eth: Mark au1000_ReleaseDB() static Johan Korsnes
2025-03-24  6:01 ` Michal Swiatkowski
2025-03-24  8:21   ` Johan Korsnes
2025-03-25  9:45     ` Jakub Kicinski [this message]
2025-03-25 15:40 ` 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=20250325024502.70a84c3f@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johan.korsnes@gmail.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --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).