All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@nabladev.com>
To: Tom Rini <trini@konsulko.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	Julien Stephan <jstephan@baylibre.com>,
	Coben Han <cobenhan@mediastek.com>, Peng Fan <peng.fan@nxp.com>
Subject: Please pull u-boot-i2c
Date: Thu, 9 Jul 2026 17:24:19 +0200	[thread overview]
Message-ID: <7f4e54a5-00ba-56d8-891a-a29f987e703c@nabladev.com> (raw)

Hello Tom,

please pull from

The following changes since commit ee5d46b45ec0c63f8f9dd1e816e0dac3452ccc3d:

   Merge branch 'next' (2026-07-06 18:26:12 -0600)

are available in the Git repository at:

   git@git.u-boot-project.org:u-boot/custodians/hs/u-boot-i2c.git tags/i2c-updates-for-2026.10-rc1

for you to fetch changes up to 0ded029735303c0db04510792bfc5f0dcc62f5af:

   cmd: kconfig: i2c: add missing I2C API dependency (2026-07-09 07:18:18 +0200)

----------------------------------------------------------------
i2c updates for 2026.10-rc1

- i2c: designware: fix i2c probe error
   from Coben

   It would be good to have some Testers...

- i2c: nx_i2c: updates from Peng

   - Added License information
   - use dev_read_addr_ptr()

- cmd: kconfig: i2c: add missing I2C API dependency
   from Julien

----------------------------------------------------------------
Coben Han (1):
       i2c: designware: fix i2c probe error

Julien Stephan (1):
       cmd: kconfig: i2c: add missing I2C API dependency

Peng Fan (2):
       i2c: nx: Use dev_read_addr_ptr()
       i2c: nx: Add License

  cmd/Kconfig                  |  1 +
  drivers/i2c/designware_i2c.c | 44 +++++++++++++++++++++++++++++++++++++++-----
  drivers/i2c/nx_i2c.c         |  9 ++++++---
  3 files changed, 46 insertions(+), 8 deletions(-)


Azure build is fine:

https://dev.azure.com/hs0298/hs/_build/results?buildId=210&view=results

Thanks!

bye,
Heiko
-- 
Nabla Software Engineering
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Geschäftsführer : Stefano Babic

             reply	other threads:[~2026-07-09 15:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 15:24 Heiko Schocher [this message]
2026-07-10  1:11 ` Please pull u-boot-i2c Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2026-08-25 11:21 Heiko Schocher
2026-08-25 20:02 ` Tom Rini
2026-08-26  4:17   ` Heiko Schocher
2026-05-14 13:36 Heiko Schocher
2026-05-14 17:55 ` Tom Rini
2026-01-07  7:15 Heiko Schocher
2026-01-07 21:07 ` Tom Rini
2024-10-21  8:27 Heiko Schocher
2024-10-21 16:39 ` Tom Rini
2024-08-08  8:42 Heiko Schocher
2024-08-08 13:58 ` Tom Rini
2024-08-08 14:06   ` Heiko Schocher
2024-08-08 14:52     ` Tom Rini
2023-11-02 14:10 Heiko Schocher
2023-11-02 14:53 ` Tom Rini
2023-08-15  7:53 Heiko Schocher
2023-08-15 16:59 ` Tom Rini
2023-06-05  7:39 Heiko Schocher
2023-06-05 19:58 ` Tom Rini
2023-06-06  4:17   ` Heiko Schocher
2023-06-06 17:29 ` Tom Rini
2023-04-11 11:04 Heiko Schocher
2023-04-11 14:42 ` Tom Rini
2023-02-13 14:52 Heiko Schocher
2023-02-13 16:28 ` Tom Rini
2022-12-05  7:30 Heiko Schocher
2022-12-05 15:58 ` Tom Rini
2022-11-14  9:12 Heiko Schocher
2022-11-14 20:44 ` Tom Rini
2022-07-19 15:24 Heiko Schocher
2022-07-20 11:10 ` Tom Rini
2022-03-23  9:16 Heiko Schocher
2022-03-23 14:22 ` Tom Rini
2021-12-20 10:14 Heiko Schocher
2021-12-20 16:16 ` Tom Rini

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=7f4e54a5-00ba-56d8-891a-a29f987e703c@nabladev.com \
    --to=hs@nabladev.com \
    --cc=cobenhan@mediastek.com \
    --cc=jstephan@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.