From: Greg KH <greg@kroah.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Cyril Brulebois <cyril@debamax.com>,
stable@vger.kernel.org, charles.fendt@me.com
Subject: Re: [PATCH 1/3] ARM: dts: add Raspberry Pi Compute Module 3 and IO board
Date: Tue, 16 Jul 2019 18:11:22 +0900 [thread overview]
Message-ID: <20190716091122.GB11964@kroah.com> (raw)
In-Reply-To: <860468a1-df13-cb6a-6951-455cf72ad4a0@i2se.com>
On Mon, Jul 15, 2019 at 05:26:16PM +0200, Stefan Wahren wrote:
> Hi Cyril,
>
> On 15.07.19 16:01, Cyril Brulebois wrote:
> > From: Stefan Wahren <stefan.wahren@i2se.com>
> >
> > commit a54fe8a6cf66828499b121c3c39c194b43b8ed94 upstream.
> >
> > The Raspberry Pi Compute Module 3 (CM3) and the Raspberry Pi
> > Compute Module 3 Lite (CM3L) are SoMs which contains a BCM2837 processor,
> > 1 GB RAM and a GPIO expander. The CM3 has a 4 GB eMMC, but on the CM3L
> > the eMMC is unpopulated and it's up to the user to connect their
> > own SD/MMC device. The dtsi file is designed to work for both modules.
> > There is also a matching carrier board which is called
> > Compute Module IO Board V3.
>
> this patch series doesn't apply to the stable kernel rules.
I'm with Stefan. Cyril, how do you think this matches up with what:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
says?
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-16 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 14:01 [PATCH 0/3] arm/arm64: Backport DTB support for Raspberry Pi Compute Module 3 to 4.19.y Cyril Brulebois
2019-07-15 14:01 ` [PATCH 1/3] ARM: dts: add Raspberry Pi Compute Module 3 and IO board Cyril Brulebois
2019-07-15 15:26 ` Stefan Wahren
2019-07-16 9:11 ` Greg KH [this message]
2019-07-17 2:04 ` Cyril Brulebois
2019-07-17 4:24 ` Greg KH
2019-07-15 14:01 ` [PATCH 2/3] arm64: dts: broadcom: Add reference to Compute Module IO Board V3 Cyril Brulebois
2019-07-15 14:01 ` [PATCH 3/3] arm64: dts: broadcom: Use the .dtb name in the rule, rather than .dts Cyril Brulebois
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=20190716091122.GB11964@kroah.com \
--to=greg@kroah.com \
--cc=charles.fendt@me.com \
--cc=cyril@debamax.com \
--cc=stable@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
/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.