From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3.1 0/3] soc: amlogic: Add Amlogic SoC Information driver
Date: Thu, 27 Jul 2017 17:29:07 -0700 [thread overview]
Message-ID: <7h4ltxs8to.fsf@baylibre.com> (raw)
In-Reply-To: <e9558b4f-b155-9f25-fe39-b876973299b5@baylibre.com> (Neil Armstrong's message of "Thu, 13 Jul 2017 12:25:20 +0200")
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 07/12/2017 09:03 PM, Martin Blumenstingl wrote:
>> Hi Kevin,
>>
>> On Fri, Jun 23, 2017 at 10:28 AM, Neil Armstrong
>> <narmstrong@baylibre.com> wrote:
>>> Amlogic SoCs have a SoC information register for SoC type, package type and
>>> revision information.
>>> This patchset adds support for this register decoding and exposing with the
>>> SoC bus infrastructure, with dt-bindings and DT node.
>> I'm curious: are you going to take this through your tree or are we
>> waiting for someone's ACK here?
>
> I'm curious also, it should go through armsoc-drivers, no ?
I was being lazy and assuming that Arnd would have another look as he
reviewed an earlier version, but since there appear to be no further
reviews/comments, I'll take it through the amlogic tree in the
v4.14/drivers branch.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3.1 0/3] soc: amlogic: Add Amlogic SoC Information driver
Date: Thu, 27 Jul 2017 17:29:07 -0700 [thread overview]
Message-ID: <7h4ltxs8to.fsf@baylibre.com> (raw)
In-Reply-To: <e9558b4f-b155-9f25-fe39-b876973299b5@baylibre.com> (Neil Armstrong's message of "Thu, 13 Jul 2017 12:25:20 +0200")
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 07/12/2017 09:03 PM, Martin Blumenstingl wrote:
>> Hi Kevin,
>>
>> On Fri, Jun 23, 2017 at 10:28 AM, Neil Armstrong
>> <narmstrong@baylibre.com> wrote:
>>> Amlogic SoCs have a SoC information register for SoC type, package type and
>>> revision information.
>>> This patchset adds support for this register decoding and exposing with the
>>> SoC bus infrastructure, with dt-bindings and DT node.
>> I'm curious: are you going to take this through your tree or are we
>> waiting for someone's ACK here?
>
> I'm curious also, it should go through armsoc-drivers, no ?
I was being lazy and assuming that Arnd would have another look as he
reviewed an earlier version, but since there appear to be no further
reviews/comments, I'll take it through the amlogic tree in the
v4.14/drivers branch.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
carlo@caione.org, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3.1 0/3] soc: amlogic: Add Amlogic SoC Information driver
Date: Thu, 27 Jul 2017 17:29:07 -0700 [thread overview]
Message-ID: <7h4ltxs8to.fsf@baylibre.com> (raw)
In-Reply-To: <e9558b4f-b155-9f25-fe39-b876973299b5@baylibre.com> (Neil Armstrong's message of "Thu, 13 Jul 2017 12:25:20 +0200")
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 07/12/2017 09:03 PM, Martin Blumenstingl wrote:
>> Hi Kevin,
>>
>> On Fri, Jun 23, 2017 at 10:28 AM, Neil Armstrong
>> <narmstrong@baylibre.com> wrote:
>>> Amlogic SoCs have a SoC information register for SoC type, package type and
>>> revision information.
>>> This patchset adds support for this register decoding and exposing with the
>>> SoC bus infrastructure, with dt-bindings and DT node.
>> I'm curious: are you going to take this through your tree or are we
>> waiting for someone's ACK here?
>
> I'm curious also, it should go through armsoc-drivers, no ?
I was being lazy and assuming that Arnd would have another look as he
reviewed an earlier version, but since there appear to be no further
reviews/comments, I'll take it through the amlogic tree in the
v4.14/drivers branch.
Kevin
next prev parent reply other threads:[~2017-07-28 0:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 8:28 [PATCH v3.1 0/3] soc: amlogic: Add Amlogic SoC Information driver Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` [PATCH v3.1 1/3] dt-bindings: arm: amlogic: Add SoC information bindings Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` [PATCH v3.1 2/3] ARM64: dts: meson-gx: Add SoC info register Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` [PATCH v3.1 3/3] soc: Add Amlogic SoC Information driver Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-06-23 8:28 ` Neil Armstrong
2017-07-12 19:03 ` [PATCH v3.1 0/3] soc: amlogic: " Martin Blumenstingl
2017-07-12 19:03 ` Martin Blumenstingl
2017-07-12 19:03 ` Martin Blumenstingl
2017-07-13 10:25 ` Neil Armstrong
2017-07-13 10:25 ` Neil Armstrong
2017-07-13 10:25 ` Neil Armstrong
2017-07-28 0:29 ` Kevin Hilman [this message]
2017-07-28 0:29 ` Kevin Hilman
2017-07-28 0:29 ` 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=7h4ltxs8to.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.