From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jorge Ramirez-Ortiz, Foundries <jorge@foundries.io>
Date: Fri, 23 Oct 2020 08:35:19 +0200
Subject: [PATCH] mx6: peripheral clock from oscillator
In-Reply-To: <CAOMZO5AeTWH4E9pXyO7Szbutc4E=zPojmaYPy6CGDMYgMU9NOg@mail.gmail.com>
References: <20201019142329.2103-1-jorge@foundries.io>
 <CAOMZO5CCnx6mu7j63Dn77mhOQG_MkokX8G_grMSvzzD45eB3EQ@mail.gmail.com>
 <20201022212444.GA4707@trex>
 <CAOMZO5AeTWH4E9pXyO7Szbutc4E=zPojmaYPy6CGDMYgMU9NOg@mail.gmail.com>
Message-ID: <20201023063519.GA20557@trex>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 22/10/20, Fabio Estevam wrote:
> On Thu, Oct 22, 2020 at 6:24 PM Jorge Ramirez-Ortiz, Foundries
> <jorge@foundries.io> wrote:
> 
> > um, weird, I just googled "imx Rev 2, 10/2019, ERR007805" and it showed
> > the document and a link to the errata.
> 
> The errata document is specific for a SoC.

perfect. now you understand my point and why I was being generic.

> 
> It does not help to add "Rev 2, 10/2019, ERR007805" in the commit log
> as we cannot know which SoC it refers to.

um, weird....the patch indicates imx6 in the name. this should be enough no?

> 
> Just mention the SoC errata document. For example: IMX6SLCE Rev. 5, 02/2019

so you need the names and versions of the errata document for each SoC being affected?
that being the case, should it be a patch per family or a patch per SoC?