Netdev List
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Prasad Pandit <ppandit@redhat.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	netdev@vger.kernel.org, Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH] dpll: indent DPLL option type by a tab
Date: Mon, 8 Apr 2024 13:24:58 +0300	[thread overview]
Message-ID: <ea7015d5-8364-400c-bb15-3a4ad254df25@moroto.mountain> (raw)
In-Reply-To: <Zf12B9rjjZotZ46C@nanopsycho>

On Fri, Mar 22, 2024 at 01:13:59PM +0100, Jiri Pirko wrote:
> Fri, Mar 22, 2024 at 12:35:21PM CET, ppandit@redhat.com wrote:
> >Hi,
> >
> >Thank you for a quick response.
> >
> >On Fri, 22 Mar 2024 at 16:41, Jiri Pirko <jiri@resnulli.us> wrote:
> >> You should indicate the target tree:
> >> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html?highlight=network#tl-dr
> >
> >* It is for the -net tree IIUC, not net-next.
> 
> Okay.
> 
> 
> >
> >> Also, please include "Fixes" tag.
> >
> >* Last time they said not to include "Fixes" tag ->
> >https://lists.infradead.org/pipermail/linux-arm-kernel/2024-March/911714.html
> 
> AFAIU and IIRC, discussed couple of times, the outcome is that Fixes
> should be included for netdev patches every time, no matter what is the
> matter of the actual fix and target tree. Please include it. For -net it
> is actually required.
> 

I think there is some confusion here.  When Prasad Pandit says it
affects "Kconfig parsers", he is talking about his out-of-tree program.
https://github.com/pjps/config-kernel  It doesn't affect anything
in-tree so we wouldn't normally give it a Fixes tag.

There is a gray area around silencing static checker warnings.  Most of
the time, people say to not include a fixes tag for that.  But sometimes
people go the other way.  In this case, it's not really a static checker
warning, it's just a white space issue.  Also Prasad should just modify
config-kernel to match the in-kernel parser.

It's true that for Fixes it doesn't matter the tree, it only matters if
it's a bugfix.  People sometimes used to say "I'm not including a Fixes
tag because this is too new for -stable kernels".  But actually having
a Fixes tag that points to a very recent bug helps the stable
maintainers automatically mark it as NOT necessary.  (The stable
maintainers do sometimes backport patches which were not explicitly
marked with a Fixes tag because people forget to tag things sometimes).

regards,
dan carpenter


      parent reply	other threads:[~2024-04-08 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 10:56 [PATCH] dpll: indent DPLL option type by a tab Prasad Pandit
2024-03-22 11:11 ` Jiri Pirko
2024-03-22 11:35   ` Prasad Pandit
2024-03-22 12:13     ` Jiri Pirko
2024-03-22 12:27       ` Prasad Pandit
2024-04-08 10:24       ` Dan Carpenter [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=ea7015d5-8364-400c-bb15-3a4ad254df25@moroto.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=pjp@fedoraproject.org \
    --cc=ppandit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox