From: Thierry Reding <thierry.reding@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: linux-tegra@vger.kernel.org, ARM-SoC Maintainers <arm@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL 0/3] arm64: tegra: Updates for v4.20-rc2
Date: Thu, 8 Nov 2018 13:16:27 +0100 [thread overview]
Message-ID: <20181108121627.GA1340@ulmo> (raw)
In-Reply-To: <CAOesGMjcOQif8H6b5afKBwYstkbzGC7wuUcN2Srz=vJz11qSnA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1598 bytes --]
On Wed, Nov 07, 2018 at 08:31:55AM -0800, Olof Johansson wrote:
> Hi Thierry,
>
> On Wed, Nov 7, 2018 at 6:53 AM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > Hi ARM SoC maintainers,
> >
> > These pull requests are some follow-up changes to finally enable the
> > generic power domains for the Tegra XUSB block. This builds on top of
> > changes that were merged into v4.20-rc1, but because of some non-
> > trivial runtime dependencies I decided to hold back on these until
> > after the dust had settled.
> >
> > Do you think it would be possible to merge these in for v4.20-rc2? I
> > realize that they are not actually fixes, but they merely add a couple
> > of lines to enable the power domains for XUSB as well as the
> > corresponding DT bindings.
>
> Is anything broken without these changes, or is it more that the
> dependency have landed and you're itching to get things enabled?
>
> If it's the former we should chat (since it's an unfortunate
> situation). If it's the latter I'm happy to queue them up for the next
> merge window.
Nothing's broken without these changes, but I figured that these two
dozen lines could still make it into v4.20. I know that this has
occasionally been done in the past for very small enablement patches
if they were small enough. I could've communicated this a little
earlier, so that this wouldn't have come as a bit of a surprise.
If you prefer to defer this to v4.21 that's totally fine. I can queue
them up in my tree for the next merge window, no need for you to pick
this up in pieces.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/3] arm64: tegra: Updates for v4.20-rc2
Date: Thu, 8 Nov 2018 13:16:27 +0100 [thread overview]
Message-ID: <20181108121627.GA1340@ulmo> (raw)
In-Reply-To: <CAOesGMjcOQif8H6b5afKBwYstkbzGC7wuUcN2Srz=vJz11qSnA@mail.gmail.com>
On Wed, Nov 07, 2018 at 08:31:55AM -0800, Olof Johansson wrote:
> Hi Thierry,
>
> On Wed, Nov 7, 2018 at 6:53 AM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > Hi ARM SoC maintainers,
> >
> > These pull requests are some follow-up changes to finally enable the
> > generic power domains for the Tegra XUSB block. This builds on top of
> > changes that were merged into v4.20-rc1, but because of some non-
> > trivial runtime dependencies I decided to hold back on these until
> > after the dust had settled.
> >
> > Do you think it would be possible to merge these in for v4.20-rc2? I
> > realize that they are not actually fixes, but they merely add a couple
> > of lines to enable the power domains for XUSB as well as the
> > corresponding DT bindings.
>
> Is anything broken without these changes, or is it more that the
> dependency have landed and you're itching to get things enabled?
>
> If it's the former we should chat (since it's an unfortunate
> situation). If it's the latter I'm happy to queue them up for the next
> merge window.
Nothing's broken without these changes, but I figured that these two
dozen lines could still make it into v4.20. I know that this has
occasionally been done in the past for very small enablement patches
if they were small enough. I could've communicated this a little
earlier, so that this wouldn't have come as a bit of a surprise.
If you prefer to defer this to v4.21 that's totally fine. I can queue
them up in my tree for the next merge window, no need for you to pick
this up in pieces.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20181108/c46528a0/attachment.sig>
next prev parent reply other threads:[~2018-11-08 12:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 14:53 [GIT PULL 0/3] arm64: tegra: Updates for v4.20-rc2 Thierry Reding
2018-11-07 14:53 ` Thierry Reding
2018-11-07 14:53 ` [GIT PULL 1/3] dt-bindings: " Thierry Reding
2018-11-07 14:53 ` Thierry Reding
2018-11-07 14:53 ` [GIT PULL 2/3] soc/tegra: " Thierry Reding
2018-11-07 14:53 ` Thierry Reding
2018-11-07 14:53 ` [GIT PULL 3/3] arm64: tegra: Device tree updates " Thierry Reding
2018-11-07 14:53 ` Thierry Reding
2018-11-07 16:31 ` [GIT PULL 0/3] arm64: tegra: Updates " Olof Johansson
2018-11-07 16:31 ` Olof Johansson
2018-11-08 12:16 ` Thierry Reding [this message]
2018-11-08 12:16 ` Thierry Reding
2018-11-13 19:29 ` Olof Johansson
2018-11-13 19:29 ` Olof Johansson
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=20181108121627.GA1340@ulmo \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
/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.