From: Jiri Pirko <jiri@resnulli.us>
To: Prasad Pandit <ppandit@redhat.com>
Cc: 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: Fri, 22 Mar 2024 13:13:59 +0100 [thread overview]
Message-ID: <Zf12B9rjjZotZ46C@nanopsycho> (raw)
In-Reply-To: <CAE8KmOx9-BgbOxV6-wDRz2XUasEzp2krqMPbVYYZbav+8dCtBw@mail.gmail.com>
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.
>
>Will send a revised patch. Thank you.
You should have waited 24 hours. Did you read:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html?highlight=network#tl-dr
?
>---
> - Prasad
>
next prev parent reply other threads:[~2024-03-22 12:14 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 [this message]
2024-03-22 12:27 ` Prasad Pandit
2024-04-08 10:24 ` Dan Carpenter
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=Zf12B9rjjZotZ46C@nanopsycho \
--to=jiri@resnulli.us \
--cc=arkadiusz.kubalewski@intel.com \
--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