All of lore.kernel.org
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: Pavel Machek <pavel@denx.de>
Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [cip-dev] [PATCH 4.19.y-cip 01/12] arm64: dts: renesas: r8a774a1-hihope-rzg2m[-ex/-ex-idk-1110wr]: Rename HiHope RZ/G2M boards
Date: Wed, 26 Aug 2020 06:32:48 +0000	[thread overview]
Message-ID: <TYBPR01MB530908ABFF44B4CA8C8D8F6786540@TYBPR01MB5309.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20200825215126.GA28711@amd>

[-- Attachment #1: Type: text/plain, Size: 2433 bytes --]

Hi Pavel,

Thanks for the feedback.

> Subject: Re: [PATCH 4.19.y-cip 01/12] arm64: dts: renesas: r8a774a1-hihope-
> rzg2m[-ex/-ex-idk-1110wr]: Rename HiHope RZ/G2M boards
>
> Hi!
>
> > > I believe it would be better to always use explicit revision in
> > > these cases; anything else is fairly confusing, as kernel update
> > > breaks your setup (aka a regresssion).
> > >
> > > Now, if -rev2 had few copies, and people really have -rev4, there
> > > will not be much breakage. But imagine if rare -rev5 is released in
> future...
> > >
> > > But mainline already made the choice. I'd just prefer not making
> > > same choice in future.
> > >
> > > Now, what to do here? One way would be to apply a series, but add a
> > > README.cip file explaining incompatible change (and any future stuff
> > > people need to know).
> >
> > OK. Either README.cip or " by including more information on the reference
> hardware and test information on CIP wiki." as suggested by Nobuhiro.
> > Please let us know, How do we want to proceed?
> >
>
> I guess we should really have README file in the tree, explaining potential
> compatibility issues and anything unusual happening in the tree. I went
> through old changelogs, and collected these for 4.19
> tree:
>
> * -cip3: MDS sampling vulnerability fixes
>
> This release includes many CVE fixes including MDS (Microarchitectural Data
> Sampling: CVE-2018-12130, CVE-2018-12126, CVE-2018-12127, CVE-2019-
> 11091). These fixes were more extensive and harder to review than usual for
> -stable tree.
>
> * -cip9: m57621-mmc driver was removed
>
> m57621-mmc driver was removed due to uncertainty about its licensing.
>
> * -cip34: Support for Renesas RZ/G2[MN] revision 4 board
>
> In -cip34, support for revision 4 of the board was merged. After the merge,
> r8a774a1-hihope-rzg2m*.dtb files are suitable for revision 4 of the board; if
> you want to produce dtb files for revision 2 of the board, append -rev2 to the
> file names.
>
> ---
>
> Does that sound ok?

Yes, It looks good to me.

Cheers,
Biju


Renesas Electronics Europe GmbH, Geschaeftsfuehrer/President: Carsten Jauch, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany, Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5257): https://lists.cip-project.org/g/cip-dev/message/5257
Mute This Topic: https://lists.cip-project.org/mt/76290781/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2020-08-26 11:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 16:36 [cip-dev] [PATCH 4.19.y-cip 00/12] Support RZ/G2[MN] rev4 board Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 01/12] arm64: dts: renesas: r8a774a1-hihope-rzg2m[-ex/-ex-idk-1110wr]: Rename HiHope RZ/G2M boards Biju Das
2020-08-19 18:05   ` Pavel Machek
2020-08-20  6:54     ` Biju Das
2020-08-23 19:35       ` Pavel Machek
2020-08-24  6:46         ` Biju Das
2020-08-25 21:51           ` Pavel Machek
2020-08-26  6:32             ` Biju Das [this message]
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 02/12] arm64: dts: renesas: r8a774b1-hihope-rzg2n[-ex]: Rename HiHope RZ/G2N boards Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 03/12] arm64: dts: renesas: hihope-common: Separate out Rev.2.0 specific into hihope-rev2.dtsi file Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 04/12] arm64: dts: renesas: Add HiHope RZ/G2M[N] Rev.3.0/4.0 specific into common file Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 05/12] arm64: dts: renesas: Add HiHope RZ/G2M Rev.3.0/4.0 main board support Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 06/12] arm64: dts: renesas: Add HiHope RZ/G2M Rev.3.0/4.0 sub " Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 07/12] arm64: dts: renesas: hihope-rzg2-ex: Separate out lvds specific nodes into common file Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 08/12] arm64: dts: renesas: Add HiHope RZ/G2M Rev.3.0/4.0 board with idk-1110wr display Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 09/12] arm64: dts: renesas: Add HiHope RZ/G2N Rev.3.0/4.0 main board support Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 10/12] arm64: dts: renesas: Add HiHope RZ/G2N Rev.3.0/4.0 sub " Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 11/12] arm64: dts: renesas: Add HiHope RZ/G2N Rev2.0/3.0/4.0 board with idk-1110wr display Biju Das
2020-08-19 16:36 ` [cip-dev] [PATCH 4.19.y-cip 12/12] arm64: dts: renesas: r8a774a1: Remove audio port node Biju Das
2020-08-19 17:38 ` [cip-dev] [PATCH 4.19.y-cip 00/12] Support RZ/G2[MN] rev4 board Pavel Machek
2020-08-20  9:16   ` Chris Paterson
2020-08-23 19:37     ` Pavel Machek
2020-08-23 23:15       ` Nobuhiro Iwamatsu

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=TYBPR01MB530908ABFF44B4CA8C8D8F6786540@TYBPR01MB5309.jpnprd01.prod.outlook.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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.