From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PULL u-boot] Please pull u-boot-amlogic-20210222
Date: Mon, 22 Feb 2021 15:03:04 -0500 [thread overview]
Message-ID: <20210222200304.GO10169@bill-the-cat> (raw)
In-Reply-To: <2417b7bc-0dad-64ce-c4a9-ed4d9851df44@baylibre.com>
On Mon, Feb 22, 2021 at 03:30:36PM +0100, Neil Armstrong wrote:
> Hi Tom,
>
> These changes adds support for reading the ADC key on the Khadas VIM3 & VIM3L, in the same
> time it adds plumbing for ADC keys and a test for sandbox.
>
> The CI job is at https://gitlab.denx.de/u-boot/custodians/u-boot-amlogic/pipelines/6461
>
> Thanks,
> Neil
>
> The following changes since commit 496f49464d90b564da5f1a2f4eecb5553e01edf9:
>
> Merge branch '2021-02-16-assorted-improvements' (2021-02-16 15:14:34 -0500)
>
> are available in the Git repository at:
>
> https://gitlab.denx.de/u-boot/custodians/u-boot-amlogic.git tags/u-boot-amlogic-20210222
>
> for you to fetch changes up to 2d339efb1ff941705a770e93494427912689ce18:
>
> button: add udevice forward declaration (2021-02-22 11:07:57 +0100)
>
First up, I've applied this to u-boot/master, as there's some small
problems, but I don't want to make you recreate the tag. That said,
running ./scripts/checkpatch.pl -q --git on this shows that the ADC
changes all add "treshold" fields, etc, and not "threshold" fields. A
follow-up to fix this, before the misspelling propagates more would be
appreciated. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210222/8f586d9d/attachment.sig>
next prev parent reply other threads:[~2021-02-22 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 14:30 [PULL u-boot] Please pull u-boot-amlogic-20210222 Neil Armstrong
2021-02-22 20:03 ` Tom Rini [this message]
2021-02-23 8:20 ` Neil Armstrong
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=20210222200304.GO10169@bill-the-cat \
--to=trini@konsulko.com \
--cc=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