From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: ARM: SoC fixes for 4.15
Date: Sat, 20 Jan 2018 09:32:52 +0100 [thread overview]
Message-ID: <20180120083252.GA23243@kroah.com> (raw)
In-Reply-To: <CAK8P3a2Ys-N3K+51gQ9Af+j+BdYR2SxJ6K24V+qz2odBzbdtAA@mail.gmail.com>
On Fri, Jan 19, 2018 at 05:12:15PM +0100, Arnd Bergmann wrote:
> The following changes since commit b2cd1df66037e7c4697c7e40496bf7e4a5e16a2d:
>
> Linux 4.15-rc7 (2018-01-07 14:22:41 -0800)
>
> are available in the git repository at:
>
> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> tags/armsoc-fixes
>
> for you to fetch changes up to b7563e2796f8b23c98afcfea7363194227fa089d:
>
> phy: work around 'phys' references to usb-nop-xceiv devices
> (2018-01-19 16:12:37 +0100)
>
> ----------------------------------------------------------------
> ARM: SoC fixes for 4.15
>
> We have various small DT fixes, and one important regression fix:
>
> The recent device tree bugfixes that were intended to address issues that
> 'dtc' started warning about in 4.15 fixed various USB PHY device nodes,
> but it turns out that we had code that depended on those nodes being
> incorrect and the probe failing with a particular error code. With the
> workaround we can also deal with correct device nodes.
>
> The DT fixes include:
> - Allwinner A10 and A20 had the display pipeline set up incorrectly
> (introduced in v4.15)
> - The Altera PMU lacked an interrupt-parent (never worked)
> - Pin muxing on the Openblocks A7 (never worked)
> - Clocks might get set up wrong on Armada 7K/8K (4.15 regression)
>
> We now have additional device tree patches to address all the remaining
> warnings introduced in 4.15, but decided to queue them for 4.16 instead,
> to avoid risking another regression like the USB PHY thing mentioned
> above.
>
> ----------------------------------------------------------------
>
> [note: I originally sent the phy-core patch to Greg with Kishon's
> ack, as drivers/phy stuff tends to go that route but got no reply
> over the last week, so I'm including it here instead. As the bug
> was introduced through arm-soc, this seems like the best way
> to now make sure we fix it before the release.]
No objection from me for this.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (gregkh)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: SoC fixes for 4.15
Date: Sat, 20 Jan 2018 09:32:52 +0100 [thread overview]
Message-ID: <20180120083252.GA23243@kroah.com> (raw)
In-Reply-To: <CAK8P3a2Ys-N3K+51gQ9Af+j+BdYR2SxJ6K24V+qz2odBzbdtAA@mail.gmail.com>
On Fri, Jan 19, 2018 at 05:12:15PM +0100, Arnd Bergmann wrote:
> The following changes since commit b2cd1df66037e7c4697c7e40496bf7e4a5e16a2d:
>
> Linux 4.15-rc7 (2018-01-07 14:22:41 -0800)
>
> are available in the git repository at:
>
> ssh://git at gitolite.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> tags/armsoc-fixes
>
> for you to fetch changes up to b7563e2796f8b23c98afcfea7363194227fa089d:
>
> phy: work around 'phys' references to usb-nop-xceiv devices
> (2018-01-19 16:12:37 +0100)
>
> ----------------------------------------------------------------
> ARM: SoC fixes for 4.15
>
> We have various small DT fixes, and one important regression fix:
>
> The recent device tree bugfixes that were intended to address issues that
> 'dtc' started warning about in 4.15 fixed various USB PHY device nodes,
> but it turns out that we had code that depended on those nodes being
> incorrect and the probe failing with a particular error code. With the
> workaround we can also deal with correct device nodes.
>
> The DT fixes include:
> - Allwinner A10 and A20 had the display pipeline set up incorrectly
> (introduced in v4.15)
> - The Altera PMU lacked an interrupt-parent (never worked)
> - Pin muxing on the Openblocks A7 (never worked)
> - Clocks might get set up wrong on Armada 7K/8K (4.15 regression)
>
> We now have additional device tree patches to address all the remaining
> warnings introduced in 4.15, but decided to queue them for 4.16 instead,
> to avoid risking another regression like the USB PHY thing mentioned
> above.
>
> ----------------------------------------------------------------
>
> [note: I originally sent the phy-core patch to Greg with Kishon's
> ack, as drivers/phy stuff tends to go that route but got no reply
> over the last week, so I'm including it here instead. As the bug
> was introduced through arm-soc, this seems like the best way
> to now make sure we fix it before the release.]
No objection from me for this.
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-20 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 16:12 ARM: SoC fixes for 4.15 Arnd Bergmann
2018-01-19 16:12 ` Arnd Bergmann
2018-01-20 8:32 ` gregkh [this message]
2018-01-20 8:32 ` gregkh
-- strict thread matches above, loose matches on Subject: below --
2018-01-04 16:46 Arnd Bergmann
2018-01-04 16:46 ` Arnd Bergmann
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=20180120083252.GA23243@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=torvalds@linux-foundation.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.