From: Otto Sabart <ottosabart@seberm.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Jonathan Corbet <corbet@lwn.net>,
Jiri Kosina <trivial@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 3/8] doc: bindings: fix bad reference to ARM CPU bindings
Date: Fri, 4 Jan 2019 10:26:40 +0100 [thread overview]
Message-ID: <20190104092640.GA21106@personal> (raw)
In-Reply-To: <CAL_JsqJW=zxvsptwEh94KP7rEMMgj_HKZ7zTVtC2y_wno_jPHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
On 03. Jan (Thursday) v 14:53:38 -0600 2019, Rob Herring wrote:
> On Thu, Jan 3, 2019 at 1:04 PM Otto Sabart <ottosabart@seberm.com> wrote:
> >
> > The primecell.txt and cpus.txt files were converted into YAML. This
> > patch updates old references with new ones.
> >
> > Fixes: d3c207eeb905 ("dt-bindings: arm: Convert primecell binding to json-schema")
> > Fixes: 672951cbd1b7 ("dt-bindings: arm: Convert cpu binding to json-schema")
> > Signed-off-by: Otto Sabart <ottosabart@seberm.com>
> > ---
> >
> > As suggested by Jon Corbet, I am *resending* this patch once again to
> > correct maintainers. There are no changes in the code since my previous
> > e-mail.
>
> Please use scripts/get_maintainers.pl so you get the right lists too.
>
> >
> > Please review.
>
> Am I supposed to apply? I don't have a clue because I've only gotten patch 3.
>
Hello Rob,
the thing is I messed up and I sent this series of patches to Jon and
linux-doc list only.
Unfortunately these patches touch multiple subsystems so I now have to
get them to correct maintainers.
What is the best thing I should do now? Should I resend (with "RESEND
PATCH" prefix in subject) *whole* series of patches to right maintainers
and lists returned by get_maintainer.pl?
In my case this scripts returns ~60 names and lists. I suppose it is not
the right thing to spam all of them... or is it?
Thank you for your time.
Ota
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-04 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 20:00 [PATCH 0/8] Fix bad references to documentation files Otto Sabart
2019-01-02 20:01 ` [PATCH 1/8] MAINTAINERS: fix bad file reference into Documentation Otto Sabart
2019-01-02 20:01 ` [PATCH 2/8] doc: filesystems: fix bad references to nonexistent ext4.rst file Otto Sabart
2019-01-02 20:01 ` [PATCH 3/8] doc: bindings: fix bad reference to ARM CPU bindings Otto Sabart
2019-01-03 18:55 ` Otto Sabart
2019-01-03 20:53 ` Rob Herring
2019-01-04 9:26 ` Otto Sabart [this message]
2019-01-04 15:52 ` Rob Herring
2019-01-02 20:01 ` [PATCH 4/8] doc: trace: fix reference to cpuidle documentation file Otto Sabart
2019-01-02 20:02 ` [PATCH 5/8] doc: gpio-mvebu: fix broken reference to cp110-system-controller0.txt file Otto Sabart
2019-01-02 20:02 ` [PATCH 6/8] doc: scsi: remove reference to tmscsim.txt file Otto Sabart
2019-01-02 20:02 ` [PATCH 7/8] doc: pinctrl: fix bad reference to pinctrl.txt file Otto Sabart
2019-01-02 20:03 ` [PATCH 8/8] doc: fix multiple broken references Otto Sabart
2019-01-03 16:28 ` [PATCH 0/8] Fix bad references to documentation files Jonathan Corbet
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=20190104092640.GA21106@personal \
--to=ottosabart@seberm.com \
--cc=airlied@linux.ie \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=jason@lakedaemon.net \
--cc=linux-doc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).