From: Kevin Hilman <khilman@baylibre.com>
To: Philipp Zabel <pza@pengutronix.de>, Jerome Brunet <jbrunet@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] reset: meson-audio-arb: add sm1 support
Date: Fri, 04 Oct 2019 07:46:47 -0700 [thread overview]
Message-ID: <7hpnjch8ko.fsf@baylibre.com> (raw)
In-Reply-To: <20191003180311.hlv7s32twzcaxj3x@pengutronix.de>
Philipp Zabel <pza@pengutronix.de> writes:
> Hi Jerome,
>
> On Tue, Oct 01, 2019 at 11:40:20AM +0200, Jerome Brunet wrote:
> [...]
>> Looks like this patchset missed v5.4-rc1.
>> Could you provide a tag with the bindings to Kevin so we can use the IDs
>> in DT until the next merge window ?
>
> Does
>
> git://git.pengutronix.de/git/pza/linux.git reset/meson-sm1-bindings
>
> work for you?
I'd prefer a tag as that's more of an indicator that it will be static,
but if you're sure that's going to be static, and is the same branch/tag
you'll be sending upstream, that will work.
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Philipp Zabel <pza@pengutronix.de>, Jerome Brunet <jbrunet@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] reset: meson-audio-arb: add sm1 support
Date: Fri, 04 Oct 2019 07:46:47 -0700 [thread overview]
Message-ID: <7hpnjch8ko.fsf@baylibre.com> (raw)
In-Reply-To: <20191003180311.hlv7s32twzcaxj3x@pengutronix.de>
Philipp Zabel <pza@pengutronix.de> writes:
> Hi Jerome,
>
> On Tue, Oct 01, 2019 at 11:40:20AM +0200, Jerome Brunet wrote:
> [...]
>> Looks like this patchset missed v5.4-rc1.
>> Could you provide a tag with the bindings to Kevin so we can use the IDs
>> in DT until the next merge window ?
>
> Does
>
> git://git.pengutronix.de/git/pza/linux.git reset/meson-sm1-bindings
>
> work for you?
I'd prefer a tag as that's more of an indicator that it will be static,
but if you're sure that's going to be static, and is the same branch/tag
you'll be sending upstream, that will work.
Kevin
next prev parent reply other threads:[~2019-10-04 14:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 13:50 [PATCH v2 0/2] reset: meson-audio-arb: add sm1 support Jerome Brunet
2019-09-05 13:50 ` Jerome Brunet
2019-09-05 13:50 ` [PATCH v2 1/2] reset: dt-bindings: meson: update arb bindings for sm1 Jerome Brunet
2019-09-05 13:50 ` Jerome Brunet
2019-09-05 13:50 ` [PATCH v2 2/2] reset: meson-audio-arb: add sm1 support Jerome Brunet
2019-09-05 13:50 ` Jerome Brunet
2019-09-05 14:26 ` [PATCH v2 0/2] " Philipp Zabel
2019-09-05 14:26 ` Philipp Zabel
2019-10-01 9:40 ` Jerome Brunet
2019-10-01 9:40 ` Jerome Brunet
2019-10-03 18:03 ` Philipp Zabel
2019-10-03 18:03 ` Philipp Zabel
2019-10-04 14:46 ` Kevin Hilman [this message]
2019-10-04 14:46 ` 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=7hpnjch8ko.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pza@pengutronix.de \
/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.