From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rahul Tanwar <rtanwar@maxlinear.com>
Cc: "bigeasy@linutronix.de" <bigeasy@linutronix.de>,
"robh@kernel.org" <robh@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-lgm-soc <linux-lgm-soc@maxlinear.com>
Subject: Re: [PATCH v3 0/4] x86/of: Fix a bug in x86 arch OF support
Date: Tue, 22 Nov 2022 14:42:03 +0200 [thread overview]
Message-ID: <Y3zDm1zaqpn8uMiV@smile.fi.intel.com> (raw)
In-Reply-To: <fee4cf31-11be-9459-7d7b-ba8729dfb356@maxlinear.com>
On Tue, Nov 22, 2022 at 10:45:12AM +0000, Rahul Tanwar wrote:
> On 22/11/2022 6:15 pm, Andy Shevchenko wrote:
> > On Tue, Nov 22, 2022 at 09:49:04AM +0000, Rahul Tanwar wrote:
...
> > I recommend to utilize my "smart" script [1] for sending series.
> > (You may take an idea from it how to prepare the Cc list close to proper
> > one)
> >
> > [1]:
> > https://github.com/andy-shev/home-bin-tools/blob/master/ge2maintainer.sh
>
> Agree on the Cc list being wrong. Thanks for the script.
>
> Quite useful. Could not understand how the script works for multiple
> commits when you take count & version as inputs.
It starts from the commit <COMMIT_HASH>~$count and goes up. So it's basically
depth from the given commit (<COMMIT_HASH>).
> Also, where does it
> create patches (format-patch)? It seems to get suitable to & cc list &
> send emails to them. And the input is COMMIT_HASH. How do i use it for a
> series with multiple commits & do i have to create patches on my own?
It creates patches automatically in the same was as it's done by
`git format-patch`. That's why it accepts a lot of the parameters
which you usually add there.
Typical use for the series is
ge2maintainer.sh -v 1 -c 4 HEAD~0 --annotate --cover-letter
Note, that your editor should be able to handle several files to edit
(e.g. vim supports that mode).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-11-22 12:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 7:39 Rahul Tanwar
2022-11-22 7:39 ` [PATCH v3 1/4] x86/of: Convert Intel's APIC bindings to YAML schema Rahul Tanwar
2022-11-22 9:10 ` Andy Shevchenko
2022-11-22 9:43 ` Rahul Tanwar
2022-11-22 10:09 ` Andy Shevchenko
2022-11-22 10:37 ` Rahul Tanwar
2022-11-23 16:02 ` Krzysztof Kozlowski
2022-11-23 17:24 ` Andy Shevchenko
2022-11-24 8:33 ` Rahul Tanwar
2022-11-22 7:39 ` [PATCH v3 2/4] x86/of: Introduce new optional bool property for lapic Rahul Tanwar
2022-11-22 7:39 ` [PATCH v3 3/4] x86/of: Replace printk(KERN_LVL) with pr_lvl() Rahul Tanwar
2022-11-22 9:14 ` Andy Shevchenko
2022-11-22 7:39 ` [PATCH v3 4/4] x86/of: Add support for boot time interrupt delivery mode configuration Rahul Tanwar
2022-11-22 9:14 ` Andy Shevchenko
2022-11-22 9:45 ` Rahul Tanwar
2022-11-22 10:10 ` Andy Shevchenko
2022-11-22 9:17 ` [PATCH v3 0/4] x86/of: Fix a bug in x86 arch OF support Andy Shevchenko
2022-11-22 9:49 ` Rahul Tanwar
2022-11-22 10:14 ` Andy Shevchenko
2022-11-22 10:45 ` Rahul Tanwar
2022-11-22 12:42 ` Andy Shevchenko [this message]
2022-11-23 9:52 ` Rahul Tanwar
2022-11-23 13:47 ` Andy Shevchenko
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=Y3zDm1zaqpn8uMiV@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lgm-soc@maxlinear.com \
--cc=mingo@redhat.com \
--cc=robh@kernel.org \
--cc=rtanwar@maxlinear.com \
--cc=tglx@linutronix.de \
--cc=x86@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®