From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Renesas changes pending in v4.19.85-rc
Date: Tue, 19 Nov 2019 23:27:57 +0100 [thread overview]
Message-ID: <20191119222757.GA8413@amd> (raw)
Hi!
v4.19.85-rc (available at
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
)
contains at least 6 patches that look relevant to Renesas
boards. They look ok to me, but you know more about Renesas hardware
than i do, and maybe second set of eyes would be useful. (Also... you
will not have to backport these :-) )
| e80fc88a837a 441f61e3aa9e | ARM: dts: rcar: Correct SATA device sizes to 2 MiB
| fd2d5f44efa2 e3da41a6c28f | arm64: dts: renesas: salvator-common: adv748x: Override secondary addresses
| 0872c56d9d73 4d76ad7d9de0 | arm64: dts: renesas: r8a77965: Attach the SYS-DMAC to the IPMMU
| 3d9c5d05904b 99584d93e301 | arm64: dts: renesas: r8a77965: Fix HS-USB compatible
| 070df3e61d15 7a590fe31748 | arm64: dts: renesas: r8a77965: Fix clock/reset for usb2_phy1
| f2ecd2865105 09938ea9d136 | phy: renesas: rcar-gen3-usb2: fix vbus_ctrl for role sysfs
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191119/c53c9365/attachment.sig>
next reply other threads:[~2019-11-19 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 22:27 Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-20 10:50 [cip-dev] Renesas changes pending in v4.19.85-rc Biju Das
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=20191119222757.GA8413@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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.