From: Mario Limonciello <mario.limonciello@amd.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>, Joe Perches <joe@perches.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
workflows@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Enable Designware XGMAC VLAN Stripping Feature 1/2] dt-bindings: net: snps,dwmac: Add description for rx-vlan-offload
Date: Tue, 25 Jul 2023 08:19:31 -0500 [thread overview]
Message-ID: <d2f7d5dd-cada-a3a2-2962-9c93d847f491@amd.com> (raw)
In-Reply-To: <CAMuHMdX0DpNSDRSJ7D85NGV2ri2kFHjTtXJE5aOaTD3jNoyc-w@mail.gmail.com>
On 7/25/23 02:33, Geert Uytterhoeven wrote:
> Hi Joe,
>
> On Tue, Jul 25, 2023 at 6:22 AM Joe Perches <joe@perches.com> wrote:
>> I do suggest you instead write wrapper scripts to get
>> the output you want rather than updating the defaults
>> for the script and update the process documentation
>> to let other people know what do to as well.
>>
>> Something akin to Mario Limonciello's suggestion back in 2022:
>>
>> https://lore.kernel.org/lkml/20220617183215.25917-1-mario.limonciello@amd.com/
>
> FTR, this is more or less what I am using to generate a script
> to send out patches:
>
> OUT=...
> echo git send-email \\ > $OUT
> # Add -cc
> # Wrap comment inside $(: ...)
> # Replace (...) in comment by [...]
> # Replace ] at EOL by ) again
> # Add continuation to EOL
> scripts/get_maintainer.pl $* | \
> tr -d \" | \
> sed -e 's/^/--cc "/' \
> -e 's/ (/" $(: /' \
> -e 's/ (/ [/' -e 's/)/]/' \
> -e 's/]$/)/' \
> -e 's/$/ \\/' | \
> tee -a $OUT
> echo "*[0-9][0-9][0-9][0-9]-*.*" >> $OUT
>
> After generation, I edit the script to
> - Replace some --cc by --to,
> - Add/remove some people,
> and run "source $OUT" to send the patches...
>
> Gr{oetje,eeting}s,
My script is great for single subsystem patches as it gets all the right
people but I've found problems whenever it crosses multiple subsystems.
Many subsystem owners want to see the whole series of patches to
understand how they interact. So the group of patches needs to be
treated together which would need the wrapper to look at all patches
instead.
next prev parent reply other threads:[~2023-07-25 13:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 6:26 [Enable Designware XGMAC VLAN Stripping Feature 0/2] Boon, Khai, Ng <boon.khai.ng
2023-07-21 6:26 ` [Enable Designware XGMAC VLAN Stripping Feature 1/2] dt-bindings: net: snps,dwmac: Add description for rx-vlan-offload Boon, Khai, Ng <boon.khai.ng
2023-07-21 10:10 ` Krzysztof Kozlowski
2023-07-21 15:28 ` Ng, Boon Khai
2023-07-21 16:21 ` Krzysztof Kozlowski
2023-07-21 16:33 ` Ng, Boon Khai
2023-07-22 1:55 ` Jakub Kicinski
2023-07-22 3:32 ` Joe Perches
2023-07-25 1:04 ` Jakub Kicinski
2023-07-25 3:53 ` Joe Perches
2023-07-25 7:33 ` Geert Uytterhoeven
2023-07-25 13:19 ` Mario Limonciello [this message]
2023-07-25 13:43 ` Joe Perches
2023-07-25 14:37 ` Krzysztof Kozlowski
2023-07-21 16:26 ` Krzysztof Kozlowski
2023-07-21 16:39 ` Ng, Boon Khai
2023-07-21 10:17 ` Shevchenko Andriy
2023-07-21 15:35 ` Ng, Boon Khai
2023-07-21 15:48 ` Shevchenko, Andriy
2023-07-21 15:51 ` Ng, Boon Khai
2023-07-21 6:26 ` [Enable Designware XGMAC VLAN Stripping Feature 2/2] net: stmmac: dwxgmac2: Add support for HW-accelerated VLAN Stripping Boon, Khai, Ng <boon.khai.ng
2023-07-21 10:11 ` Krzysztof Kozlowski
2023-07-21 15:30 ` Ng, Boon Khai
2023-07-21 15:59 ` Florian Fainelli
2023-07-21 16:12 ` Ng, Boon Khai
2023-07-21 16:29 ` Florian Fainelli
2023-07-21 16:45 ` Ng, Boon Khai
2023-07-21 16:22 ` Krzysztof Kozlowski
2023-07-21 16:22 ` Krzysztof Kozlowski
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=d2f7d5dd-cada-a3a2-2962-9c93d847f491@amd.com \
--to=mario.limonciello@amd.com \
--cc=geert@linux-m68k.org \
--cc=joe@perches.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=workflows@vger.kernel.org \
/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
all inboxes | Powered by JetHome®