From: Jorge Ramirez-Ortiz, Foundries <jorge@foundries.io>
To: u-boot@lists.denx.de
Subject: [PATCH] mx6: peripheral clock from oscillator
Date: Fri, 23 Oct 2020 08:35:19 +0200 [thread overview]
Message-ID: <20201023063519.GA20557@trex> (raw)
In-Reply-To: <CAOMZO5AeTWH4E9pXyO7Szbutc4E=zPojmaYPy6CGDMYgMU9NOg@mail.gmail.com>
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?
next prev parent reply other threads:[~2020-10-23 6:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 14:23 [PATCH] mx6: peripheral clock from oscillator Jorge Ramirez-Ortiz
2020-10-22 15:18 ` Jorge
2020-10-22 20:51 ` Fabio Estevam
2020-10-22 21:24 ` Jorge
2020-10-22 21:30 ` Fabio Estevam
2020-10-23 6:35 ` Jorge [this message]
2020-10-23 12:13 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2020-10-14 13:07 Jorge Ramirez-Ortiz
2020-10-16 12:41 ` Jorge
2020-10-19 6:40 ` Peng Fan
2020-10-19 12:32 ` Fabio Estevam
2020-10-19 12:57 ` Jorge
2020-10-19 14:24 ` Jorge
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=20201023063519.GA20557@trex \
--to=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox