devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: robin <robin@protonic.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] auxdisplay: ht16k33: Improvement, fix, and json-schema conversion
Date: Mon, 18 Jan 2021 14:36:50 +0100	[thread overview]
Message-ID: <14593d82cd227439a9763d6277186f76@protonic.nl> (raw)
In-Reply-To: <20210118123538.564597-1-geert@linux-m68k.org>

Hi Geert,

Thank you for (re-)submitting your patches!

On 2021-01-18 13:35, Geert Uytterhoeven wrote:
> Hi Robin, Rob, Miguel,
> 
> This patch series contains various updates for the Holtek HT16K33 LED
> controller with keyscan DT bindings and driver:
>   1. Make the keypad function optional, from an old patch by Robin that 
> seem to
>      have fallen through the cracks,

Thanks for digging this up. Not sure why this was dropped. I still think 
it's usefull.

>   2. Fix the default brightness range,

Seems to match MIN/MAX_BRIGHTNESS now.
Acked-by: Robin van der Gracht <robin@protonic.nl>

Robin

  parent reply	other threads:[~2021-01-18 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 12:35 [PATCH 0/3] auxdisplay: ht16k33: Improvement, fix, and json-schema conversion Geert Uytterhoeven
2021-01-18 12:35 ` [PATCH 1/3] dt-bindings: auxdisplay: ht16k33: Keyscan function should be optional Geert Uytterhoeven
2021-01-25 21:19   ` Miguel Ojeda
2021-01-18 12:35 ` [PATCH 2/3] dt-bindings: auxdisplay: ht16k33: Fix default-brightness-level range Geert Uytterhoeven
2021-01-25 21:20   ` Miguel Ojeda
2021-01-18 12:35 ` [PATCH 3/3] dt-bindings: auxdisplay: ht16k33: Convert to json-schema Geert Uytterhoeven
2021-01-25 21:20   ` Miguel Ojeda
2021-01-18 13:36 ` robin [this message]
2021-01-23 12:47   ` [PATCH 0/3] auxdisplay: ht16k33: Improvement, fix, and json-schema conversion Miguel Ojeda

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=14593d82cd227439a9763d6277186f76@protonic.nl \
    --to=robin@protonic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=robh+dt@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).