Linux I2C development
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Max Staudt <max@enpas.org>,
	 linux-i2c@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org,
	 "Christian A. Ehrhardt" <christian.ehrhardt@codasip.com>,
	"Christian A. Ehrhardt" <lk@c--e.de>
Subject: Re: [PATCH v1 4/8] i2c: icy:pick  Use named initializer for zorro_device_id arrays
Date: Fri, 29 May 2026 00:35:35 +0200	[thread overview]
Message-ID: <ahjDIH9UlDicPYLB@zenone.zhora.eu> (raw)
In-Reply-To: <3d7690c7a8948f977d6c50bd0c8010efb715fbdc.1779803053.git.u.kleine-koenig@baylibre.com>

Hi Uwe,

On Tue, May 26, 2026 at 04:17:30PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> Using named initializers is more explicit and thus easier to parse for a
> human.
> 
> While touching this array, drop explicit zeros from the list terminator.
> 
> This change doesn't introduce changes to the compiled zorro_device_id
> array.
> 
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>

just this patch merged to i2c/i2c-host.

Thanks,
Andi

  parent reply	other threads:[~2026-05-28 22:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 14:17 [PATCH v1 0/8] zorro: Improve handling of pointers in zorro_device_id::driver_data Uwe Kleine-König (The Capable Hub)
2026-05-26 14:17 ` [PATCH v1 4/8] i2c: icy:pick Use named initializer for zorro_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-05-27 13:16   ` Geert Uytterhoeven
2026-05-28  7:48   ` Max Staudt
2026-05-28 22:35   ` Andi Shyti [this message]
2026-05-26 14:17 ` [PATCH v1 6/8] zorro: Simplify storing pointers in device id struct Uwe Kleine-König (The Capable Hub)
2026-05-27 13:18   ` Geert Uytterhoeven
2026-05-28  7:50   ` Max Staudt
2026-05-26 15:01 ` [PATCH v1 0/8] zorro: Improve handling of pointers in zorro_device_id::driver_data Geert Uytterhoeven
2026-05-26 16:38   ` Uwe Kleine-König (The Capable Hub)
2026-05-29  1:20 ` patchwork-bot+netdevbpf
2026-06-04 22:44 ` Helge Deller
2026-06-05 11:56   ` Uwe Kleine-König (The Capable Hub)

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=ahjDIH9UlDicPYLB@zenone.zhora.eu \
    --to=andi.shyti@kernel.org \
    --cc=christian.ehrhardt@codasip.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=lk@c--e.de \
    --cc=max@enpas.org \
    --cc=u.kleine-koenig@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox