All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 00/14] arm64: dts: meson-axg: add audio support
Date: Thu, 26 Jul 2018 16:38:10 -0500	[thread overview]
Message-ID: <7hfu051xvh.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCB_fULnmrpyzNwnfAiL9QGco_6QW957Wroj8o6ZhNwmWA@mail.gmail.com> (Martin Blumenstingl's message of "Wed, 25 Jul 2018 23:26:27 +0200")

Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:

> Hi Jerome,
>
> On Wed, Jul 25, 2018 at 11:19 PM <jbrunet@baylibre.com> wrote:
>>
>> On Wed, 2018-07-25 at 21:11 +0200, Martin Blumenstingl wrote:
>> > nit-pick: one patch uses "arm64: dts: meson-axg: s400" in the subject
>> > while other patches that are touching the s400 board aren't
>> > if you have to re-send this series: can you please use the "arm64:
>> > dts: meson-axg: s400:" prefix for all patches touching the s400 board?
>>
>> hum, do we really have such rule, or do you think we should add one ?
> looking at the git history in arch/arm64/boot/dts/amlogic: it seems
> that we don't have a rule yet, even though some (some of
> your's/Neil's/my) patches were using that naming schema in the past
>
>> Kevin, do you have opinion ?
>>
>> Not that I really mind either way, but prefixes rules are usually there to help
>> maintainer filter the patches. Will such rule help in any way ?
> maybe it's just a problem of a false initial impression
> I read "arm64: dts: meson-axg: add usb power regulator" in the
> cover-letter and came to the conclusion that this patch must be wrong
> since meson-axg.dtsi should not have any regulators (unless they're
> built into the SoC). only when looking at the patch itself I realized
> that it's fine because it patches the s400.dts

I actually had the same first impression problem.  At first glance, it
looks like all the patches are AXG-generic, and only the 2 that mention
s400 apply to the board.

So, if this needs a respin, I'd prefer the board name where appropriate,
but it's not something I'm going to be picky about.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/14] arm64: dts: meson-axg: add audio support
Date: Thu, 26 Jul 2018 16:38:10 -0500	[thread overview]
Message-ID: <7hfu051xvh.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCB_fULnmrpyzNwnfAiL9QGco_6QW957Wroj8o6ZhNwmWA@mail.gmail.com> (Martin Blumenstingl's message of "Wed, 25 Jul 2018 23:26:27 +0200")

Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:

> Hi Jerome,
>
> On Wed, Jul 25, 2018 at 11:19 PM <jbrunet@baylibre.com> wrote:
>>
>> On Wed, 2018-07-25 at 21:11 +0200, Martin Blumenstingl wrote:
>> > nit-pick: one patch uses "arm64: dts: meson-axg: s400" in the subject
>> > while other patches that are touching the s400 board aren't
>> > if you have to re-send this series: can you please use the "arm64:
>> > dts: meson-axg: s400:" prefix for all patches touching the s400 board?
>>
>> hum, do we really have such rule, or do you think we should add one ?
> looking at the git history in arch/arm64/boot/dts/amlogic: it seems
> that we don't have a rule yet, even though some (some of
> your's/Neil's/my) patches were using that naming schema in the past
>
>> Kevin, do you have opinion ?
>>
>> Not that I really mind either way, but prefixes rules are usually there to help
>> maintainer filter the patches. Will such rule help in any way ?
> maybe it's just a problem of a false initial impression
> I read "arm64: dts: meson-axg: add usb power regulator" in the
> cover-letter and came to the conclusion that this patch must be wrong
> since meson-axg.dtsi should not have any regulators (unless they're
> built into the SoC). only when looking at the patch itself I realized
> that it's fine because it patches the s400.dts

I actually had the same first impression problem.  At first glance, it
looks like all the patches are AXG-generic, and only the 2 that mention
s400 apply to the board.

So, if this needs a respin, I'd prefer the board name where appropriate,
but it's not something I'm going to be picky about.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: jbrunet@baylibre.com, carlo@caione.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	p.zabel@pengutronix.de, linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/14] arm64: dts: meson-axg: add audio support
Date: Thu, 26 Jul 2018 16:38:10 -0500	[thread overview]
Message-ID: <7hfu051xvh.fsf@baylibre.com> (raw)
In-Reply-To: <CAFBinCB_fULnmrpyzNwnfAiL9QGco_6QW957Wroj8o6ZhNwmWA@mail.gmail.com> (Martin Blumenstingl's message of "Wed, 25 Jul 2018 23:26:27 +0200")

Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:

> Hi Jerome,
>
> On Wed, Jul 25, 2018 at 11:19 PM <jbrunet@baylibre.com> wrote:
>>
>> On Wed, 2018-07-25 at 21:11 +0200, Martin Blumenstingl wrote:
>> > nit-pick: one patch uses "arm64: dts: meson-axg: s400" in the subject
>> > while other patches that are touching the s400 board aren't
>> > if you have to re-send this series: can you please use the "arm64:
>> > dts: meson-axg: s400:" prefix for all patches touching the s400 board?
>>
>> hum, do we really have such rule, or do you think we should add one ?
> looking at the git history in arch/arm64/boot/dts/amlogic: it seems
> that we don't have a rule yet, even though some (some of
> your's/Neil's/my) patches were using that naming schema in the past
>
>> Kevin, do you have opinion ?
>>
>> Not that I really mind either way, but prefixes rules are usually there to help
>> maintainer filter the patches. Will such rule help in any way ?
> maybe it's just a problem of a false initial impression
> I read "arm64: dts: meson-axg: add usb power regulator" in the
> cover-letter and came to the conclusion that this patch must be wrong
> since meson-axg.dtsi should not have any regulators (unless they're
> built into the SoC). only when looking at the patch itself I realized
> that it's fine because it patches the s400.dts

I actually had the same first impression problem.  At first glance, it
looks like all the patches are AXG-generic, and only the 2 that mention
s400 apply to the board.

So, if this needs a respin, I'd prefer the board name where appropriate,
but it's not something I'm going to be picky about.

Kevin

  reply	other threads:[~2018-07-26 21:38 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 12:52 [PATCH 00/14] arm64: dts: meson-axg: add audio support Jerome Brunet
2018-07-24 12:52 ` Jerome Brunet
2018-07-24 12:52 ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 01/14] arm64: dts: meson-axg: improve power supplies description Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 02/14] arm64: dts: meson-axg: add vcc 5v regulator on the s400 Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 03/14] arm64: dts: meson-axg: add usb power regulator Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 04/14] arm64: dts: meson-axg: add audio arb reset controller Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 05/14] arm64: dts: meson-axg: add audio fifos Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 06/14] arm64: dts: meson-axg: add spdifout Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 07/14] arm64: dts: meson-axg: add tdmin formatters Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 08/14] arm64: dts: meson-axg: add tdmout formatters Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 09/14] arm64: dts: meson-axg: add tdm interfaces Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 10/14] arm64: dts: meson-axg: add linein codec Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-25 19:18   ` Martin Blumenstingl
2018-07-25 19:18     ` Martin Blumenstingl
2018-07-25 19:18     ` Martin Blumenstingl
2018-07-25 22:07     ` jbrunet at baylibre.com
2018-07-25 22:07       ` jbrunet
2018-07-25 22:07       ` jbrunet at baylibre.com
2018-07-24 12:52 ` [PATCH 11/14] arm64: dts: meson-axg: add lineout codec Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 12/14] arm64: dts: meson-axg: add spdif-dit codec Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 13/14] arm64: dts: meson-axg: s400: enable audio devices Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52 ` [PATCH 14/14] arm64: dts: meson-axg: add s400 sound card Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-24 12:52   ` Jerome Brunet
2018-07-25 19:11 ` [PATCH 00/14] arm64: dts: meson-axg: add audio support Martin Blumenstingl
2018-07-25 19:11   ` Martin Blumenstingl
2018-07-25 19:11   ` Martin Blumenstingl
2018-07-25 21:19   ` jbrunet at baylibre.com
2018-07-25 21:19     ` jbrunet
2018-07-25 21:19     ` jbrunet at baylibre.com
2018-07-25 21:26     ` Martin Blumenstingl
2018-07-25 21:26       ` Martin Blumenstingl
2018-07-25 21:26       ` Martin Blumenstingl
2018-07-26 21:38       ` Kevin Hilman [this message]
2018-07-26 21:38         ` Kevin Hilman
2018-07-26 21:38         ` Kevin Hilman

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=7hfu051xvh.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=linus-amlogic@lists.infradead.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.