All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-amlogic@lists.infradead.org,
	Carlo Caione <carlo@caione.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Rob Herring <robh@kernel.org>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH v2 00/18] ARM64: meson: DT cleanups
Date: Wed, 17 May 2017 14:46:02 -0700	[thread overview]
Message-ID: <m2mvab88dh.fsf@baylibre.com> (raw)
In-Reply-To: <20170513143337.14278-1-afaerber@suse.de> ("Andreas =?utf-8?Q?F=C3=A4rber=22's?= message of "Sat, 13 May 2017 16:33:19 +0200")

Hi Andreas,

Andreas Färber <afaerber@suse.de> writes:

> This series fixes several cosmetic issues, on top of your for-next branch.
>
> Patches 3-6 rename a node, the rest should all be non-functional changes.
>
> PLEASE STOP merging random new nodes at the bottom of DT files!
> Just like it's a convention to sort new nodes by unit address, it has been
> a convention to sort by-label nodes by their label. As discussed here and
> elsewhere, this helps avoid merge conflicts and makes nodes easy to find.
> I don't care whether we order A0 before A or after, but adding new HDMI
> or CVBS nodes at the very bottom is totally out of alphabetical order.
> Since my v1 you really should've known that...

Your tone is a bit tiresome and frankly makes me hesitate before
reviewing the patches.  If you expect cordial dialogue and producitve
collaboration, please dial the accusations back a notch.

[ ... deep breath ... ]

Yes, your point was clear in v1, but that doesn't mean I agreed with it,
or that I particularily pay attention to that in my reviews because
honestly, alphabetical sorting is not very high on the list of things I
care about.  Over many years of being a kernel maintainer, I've had to
deal with my share of headaches, but conflicts caused by poorly sorted
DT files hs never been on my list of pain points.

That being said, I understand your concerns and similar ones raised
maintainers on other platforms.  I'm not a big fan of the churn caused
by this kind of rework, *but* I'm also not opposed to keeping things
better organized.  So, since there is an active contributor (and
reviewer) that is willing to put in the time and effort to clean things
up, I don't see a good (enough) reason to say no.

So, I will apply the series as is to my v4.13/dt64 branch

Going forward, I will try to keep an eye on the organization of DTS
files, but honestly, it's low priority for me, so if this is something
you care about, I trust that you will continue to help review DTS files.

I know you're already doing many reviews along with your contributions,
so thanks for that, and please keep it up. :)

> Similarly, Khadas Vim shouldn't have been merged with the "bcrmf" typo.
>
> Which proves my point that we need to fix these issues now so that they
> don't keep spreading (Broken Window Theory). New boards have not been
> checked for sort order, only boards already touched in v1.
>
> Board and Makefile order affect my pending R-Box Pro patches.
> Node order affects Martin's pending Bluetooth patches among others.

Yes, this series will affect a few other series that are in flight, and
I apologize to those developers for the needed rebase, but I'd rather
apply a series like this that affects so many DT files early in the
cycle.

Thanks again for the fixes and cleanups,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>
Cc: linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Carlo Caione <carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Neil Armstrong
	<narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
	Martin Blumenstingl
	<martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Subject: Re: [PATCH v2 00/18] ARM64: meson: DT cleanups
Date: Wed, 17 May 2017 14:46:02 -0700	[thread overview]
Message-ID: <m2mvab88dh.fsf@baylibre.com> (raw)
In-Reply-To: <20170513143337.14278-1-afaerber-l3A5Bk7waGM@public.gmane.org> ("Andreas =?utf-8?Q?F=C3=A4rber=22's?= message of "Sat, 13 May 2017 16:33:19 +0200")

Hi Andreas,

Andreas Färber <afaerber-l3A5Bk7waGM@public.gmane.org> writes:

> This series fixes several cosmetic issues, on top of your for-next branch.
>
> Patches 3-6 rename a node, the rest should all be non-functional changes.
>
> PLEASE STOP merging random new nodes at the bottom of DT files!
> Just like it's a convention to sort new nodes by unit address, it has been
> a convention to sort by-label nodes by their label. As discussed here and
> elsewhere, this helps avoid merge conflicts and makes nodes easy to find.
> I don't care whether we order A0 before A or after, but adding new HDMI
> or CVBS nodes at the very bottom is totally out of alphabetical order.
> Since my v1 you really should've known that...

Your tone is a bit tiresome and frankly makes me hesitate before
reviewing the patches.  If you expect cordial dialogue and producitve
collaboration, please dial the accusations back a notch.

[ ... deep breath ... ]

Yes, your point was clear in v1, but that doesn't mean I agreed with it,
or that I particularily pay attention to that in my reviews because
honestly, alphabetical sorting is not very high on the list of things I
care about.  Over many years of being a kernel maintainer, I've had to
deal with my share of headaches, but conflicts caused by poorly sorted
DT files hs never been on my list of pain points.

That being said, I understand your concerns and similar ones raised
maintainers on other platforms.  I'm not a big fan of the churn caused
by this kind of rework, *but* I'm also not opposed to keeping things
better organized.  So, since there is an active contributor (and
reviewer) that is willing to put in the time and effort to clean things
up, I don't see a good (enough) reason to say no.

So, I will apply the series as is to my v4.13/dt64 branch

Going forward, I will try to keep an eye on the organization of DTS
files, but honestly, it's low priority for me, so if this is something
you care about, I trust that you will continue to help review DTS files.

I know you're already doing many reviews along with your contributions,
so thanks for that, and please keep it up. :)

> Similarly, Khadas Vim shouldn't have been merged with the "bcrmf" typo.
>
> Which proves my point that we need to fix these issues now so that they
> don't keep spreading (Broken Window Theory). New boards have not been
> checked for sort order, only boards already touched in v1.
>
> Board and Makefile order affect my pending R-Box Pro patches.
> Node order affects Martin's pending Bluetooth patches among others.

Yes, this series will affect a few other series that are in flight, and
I apologize to those developers for the needed rebase, but I'd rather
apply a series like this that affects so many DT files early in the
cycle.

Thanks again for the fixes and cleanups,

Kevin
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 00/18] ARM64: meson: DT cleanups
Date: Wed, 17 May 2017 14:46:02 -0700	[thread overview]
Message-ID: <m2mvab88dh.fsf@baylibre.com> (raw)
In-Reply-To: <20170513143337.14278-1-afaerber@suse.de> ("Andreas =?utf-8?Q?F=C3=A4rber=22's?= message of "Sat, 13 May 2017 16:33:19 +0200")

Hi Andreas,

Andreas F?rber <afaerber@suse.de> writes:

> This series fixes several cosmetic issues, on top of your for-next branch.
>
> Patches 3-6 rename a node, the rest should all be non-functional changes.
>
> PLEASE STOP merging random new nodes at the bottom of DT files!
> Just like it's a convention to sort new nodes by unit address, it has been
> a convention to sort by-label nodes by their label. As discussed here and
> elsewhere, this helps avoid merge conflicts and makes nodes easy to find.
> I don't care whether we order A0 before A or after, but adding new HDMI
> or CVBS nodes at the very bottom is totally out of alphabetical order.
> Since my v1 you really should've known that...

Your tone is a bit tiresome and frankly makes me hesitate before
reviewing the patches.  If you expect cordial dialogue and producitve
collaboration, please dial the accusations back a notch.

[ ... deep breath ... ]

Yes, your point was clear in v1, but that doesn't mean I agreed with it,
or that I particularily pay attention to that in my reviews because
honestly, alphabetical sorting is not very high on the list of things I
care about.  Over many years of being a kernel maintainer, I've had to
deal with my share of headaches, but conflicts caused by poorly sorted
DT files hs never been on my list of pain points.

That being said, I understand your concerns and similar ones raised
maintainers on other platforms.  I'm not a big fan of the churn caused
by this kind of rework, *but* I'm also not opposed to keeping things
better organized.  So, since there is an active contributor (and
reviewer) that is willing to put in the time and effort to clean things
up, I don't see a good (enough) reason to say no.

So, I will apply the series as is to my v4.13/dt64 branch

Going forward, I will try to keep an eye on the organization of DTS
files, but honestly, it's low priority for me, so if this is something
you care about, I trust that you will continue to help review DTS files.

I know you're already doing many reviews along with your contributions,
so thanks for that, and please keep it up. :)

> Similarly, Khadas Vim shouldn't have been merged with the "bcrmf" typo.
>
> Which proves my point that we need to fix these issues now so that they
> don't keep spreading (Broken Window Theory). New boards have not been
> checked for sort order, only boards already touched in v1.
>
> Board and Makefile order affect my pending R-Box Pro patches.
> Node order affects Martin's pending Bluetooth patches among others.

Yes, this series will affect a few other series that are in flight, and
I apologize to those developers for the needed rebase, but I'd rather
apply a series like this that affects so many DT files early in the
cycle.

Thanks again for the fixes and cleanups,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 00/18] ARM64: meson: DT cleanups
Date: Wed, 17 May 2017 14:46:02 -0700	[thread overview]
Message-ID: <m2mvab88dh.fsf@baylibre.com> (raw)
In-Reply-To: <20170513143337.14278-1-afaerber@suse.de> ("Andreas =?utf-8?Q?F=C3=A4rber=22's?= message of "Sat, 13 May 2017 16:33:19 +0200")

Hi Andreas,

Andreas F?rber <afaerber@suse.de> writes:

> This series fixes several cosmetic issues, on top of your for-next branch.
>
> Patches 3-6 rename a node, the rest should all be non-functional changes.
>
> PLEASE STOP merging random new nodes at the bottom of DT files!
> Just like it's a convention to sort new nodes by unit address, it has been
> a convention to sort by-label nodes by their label. As discussed here and
> elsewhere, this helps avoid merge conflicts and makes nodes easy to find.
> I don't care whether we order A0 before A or after, but adding new HDMI
> or CVBS nodes at the very bottom is totally out of alphabetical order.
> Since my v1 you really should've known that...

Your tone is a bit tiresome and frankly makes me hesitate before
reviewing the patches.  If you expect cordial dialogue and producitve
collaboration, please dial the accusations back a notch.

[ ... deep breath ... ]

Yes, your point was clear in v1, but that doesn't mean I agreed with it,
or that I particularily pay attention to that in my reviews because
honestly, alphabetical sorting is not very high on the list of things I
care about.  Over many years of being a kernel maintainer, I've had to
deal with my share of headaches, but conflicts caused by poorly sorted
DT files hs never been on my list of pain points.

That being said, I understand your concerns and similar ones raised
maintainers on other platforms.  I'm not a big fan of the churn caused
by this kind of rework, *but* I'm also not opposed to keeping things
better organized.  So, since there is an active contributor (and
reviewer) that is willing to put in the time and effort to clean things
up, I don't see a good (enough) reason to say no.

So, I will apply the series as is to my v4.13/dt64 branch

Going forward, I will try to keep an eye on the organization of DTS
files, but honestly, it's low priority for me, so if this is something
you care about, I trust that you will continue to help review DTS files.

I know you're already doing many reviews along with your contributions,
so thanks for that, and please keep it up. :)

> Similarly, Khadas Vim shouldn't have been merged with the "bcrmf" typo.
>
> Which proves my point that we need to fix these issues now so that they
> don't keep spreading (Broken Window Theory). New boards have not been
> checked for sort order, only boards already touched in v1.
>
> Board and Makefile order affect my pending R-Box Pro patches.
> Node order affects Martin's pending Bluetooth patches among others.

Yes, this series will affect a few other series that are in flight, and
I apologize to those developers for the needed rebase, but I'd rather
apply a series like this that affects so many DT files early in the
cycle.

Thanks again for the fixes and cleanups,

Kevin

  parent reply	other threads:[~2017-05-17 21:46 UTC|newest]

Thread overview: 178+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13 14:33 [PATCH v2 00/18] ARM64: meson: DT cleanups Andreas Färber
2017-05-13 14:33 ` Andreas Färber
2017-05-13 14:33 ` Andreas Färber
2017-05-13 14:33 ` [PATCH v2 01/18] dt-bindings: arm: amlogic: Reorder boards Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:07   ` Neil Armstrong
2017-05-15  8:07     ` Neil Armstrong
2017-05-15  8:07     ` Neil Armstrong
2017-05-19  1:27   ` Rob Herring
2017-05-19  1:27     ` Rob Herring
2017-05-19  1:27     ` Rob Herring
2017-05-19  1:27     ` Rob Herring
2017-05-13 14:33 ` [PATCH v2 02/18] arm64: dts: amlogic: Sort Makefile Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-14  4:28   ` Chris Moore
2017-05-14  4:28     ` Chris Moore
2017-05-14  4:28     ` Chris Moore
2017-05-14  4:28     ` Chris Moore
2017-05-14 10:06     ` Andreas Färber
2017-05-14 10:06       ` Andreas Färber
2017-05-14 10:06       ` Andreas Färber
2017-05-14 10:06       ` Andreas Färber
2017-05-13 14:33 ` [PATCH v2 03/18] arm64: dts: meson-gxbb-vega-s95: Fix Wifi node name Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 04/18] arm64: dts: meson-gxbb-p20x: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 05/18] arm64: dts: meson-gx-p23x-q20x: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 06/18] arm64: dts: meson-gxl-s905x-khadas-vim: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15 20:16   ` Martin Blumenstingl
2017-05-15 20:16     ` Martin Blumenstingl
2017-05-15 20:16     ` Martin Blumenstingl
2017-05-15 20:16     ` Martin Blumenstingl
2017-05-13 14:33 ` [PATCH v2 07/18] arm64: dts: meson-gxm-nexbox-a1: Drop UART comment Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 08/18] arm64: dts: meson-gxl-s905x: Comment typo fix Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 09/18] arm64: dts: meson-gxbb-wetek-hub: Reference CVBS node by label Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 10/18] arm64: dts: meson-gxbb: Fix node order Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15 18:56     ` Andreas Färber
2017-05-15 18:56       ` Andreas Färber
2017-05-15 18:56       ` Andreas Färber
2017-05-13 14:33 ` [PATCH v2 11/18] arm64: dts: meson-gxbb-odroidc2: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 12/18] arm64: dts: meson-gxbb-vega-s95: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 13/18] arm64: dts: meson-gxbb-nexbox-a95x: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 14/18] arm64: dts: meson-gxbb-p20x: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 15/18] arm64: dts: meson-gxl: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 16/18] arm64: dts: meson-gxl-s905x-nexbox-a95x: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:17   ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-15  8:17     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 17/18] arm64: dts: meson-gxm-nexbox-a1: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:16   ` Neil Armstrong
2017-05-15  8:16     ` Neil Armstrong
2017-05-15  8:16     ` Neil Armstrong
2017-05-15  8:16     ` Neil Armstrong
2017-05-13 14:33 ` [PATCH v2 18/18] arm64: dts: meson-gx-p23x-q20x: " Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-13 14:33   ` Andreas Färber
2017-05-15  8:16   ` Neil Armstrong
2017-05-15  8:16     ` Neil Armstrong
2017-05-15  8:16     ` Neil Armstrong
2017-05-15  8:16     ` Neil Armstrong
2017-05-15  8:16 ` [PATCH v2 00/18] ARM64: meson: DT cleanups Neil Armstrong
2017-05-15  8:16   ` Neil Armstrong
2017-05-15  8:16   ` Neil Armstrong
2017-05-15 19:10   ` Andreas Färber
2017-05-15 19:10     ` Andreas Färber
2017-05-15 19:10     ` Andreas Färber
2017-05-15 19:10     ` Andreas Färber
2017-05-15 20:24     ` Martin Blumenstingl
2017-05-15 20:24       ` Martin Blumenstingl
2017-05-15 20:24       ` Martin Blumenstingl
2017-05-15 20:24       ` Martin Blumenstingl
2017-05-20 13:50       ` Andreas Färber
2017-05-20 13:50         ` Andreas Färber
2017-05-20 13:50         ` Andreas Färber
2017-05-20 13:50         ` Andreas Färber
2017-05-17 22:34     ` Kevin Hilman
2017-05-17 22:34       ` Kevin Hilman
2017-05-17 22:34       ` Kevin Hilman
2017-05-17 22:34       ` Kevin Hilman
2017-05-20 13:16       ` Andreas Färber
2017-05-20 13:16         ` Andreas Färber
2017-05-20 13:16         ` Andreas Färber
2017-05-20 13:16         ` Andreas Färber
2017-05-25 21:22         ` Carlo Caione
2017-05-25 21:22           ` Carlo Caione
2017-05-25 21:22           ` Carlo Caione
2017-05-25 21:22           ` Carlo Caione
2017-05-17 21:46 ` Kevin Hilman [this message]
2017-05-17 21:46   ` Kevin Hilman
2017-05-17 21:46   ` Kevin Hilman
2017-05-17 21:46   ` Kevin Hilman
2017-05-20 15:48   ` Andreas Färber
2017-05-20 15:48     ` Andreas Färber
2017-05-20 15:48     ` Andreas Färber
2017-05-20 15:48     ` Andreas Färber

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=m2mvab88dh.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=afaerber@suse.de \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=narmstrong@baylibre.com \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.