U-Boot Archive on 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>,
	Marek Vasut <marek.vasut@mailbox.org>
Subject: Please pull u-boot-i2c
Date: Thu, 14 May 2026 15:36:51 +0200	[thread overview]
Message-ID: <1f922957-e56d-1187-4441-e98e9f8fe25e@nabladev.com> (raw)

Hello Tom,

The following changes since commit 36d4c653580824b16574560b21d4401614d8b68e:

   virtio: fix return value check (2026-05-12 12:38:49 -0600)

are available in the Git repository at:

   https://source.denx.de/u-boot/custodians/u-boot-i2c.git tags/i2c-updates-for-2026.07-rc3

for you to fetch changes up to 0c464b6cc3ead31a5b3bfe23d38871380f3fb6fa:

   i2c: Remove legacy CONFIG_SYS_I2C_SOFT (2026-05-14 11:17:20 +0200)

----------------------------------------------------------------
updates for 2026.07-rc3

- designware_i2c: Staticize driver ops from Marek
- i2c: Remove legacy CONFIG_SYS_I2C_SOFT
-

----------------------------------------------------------------
Marek Vasut (1):
       i2c: designware_i2c: Staticize driver ops

Tom Rini (1):
       i2c: Remove legacy CONFIG_SYS_I2C_SOFT

  README                           |  92 ---------------------------------
  board/nxp/m53017evb/README       |   4 --
  board/nxp/m5373evb/README        |   4 --
  drivers/i2c/Kconfig              |  20 --------
  drivers/i2c/Makefile             |   1 -
  drivers/i2c/designware_i2c_pci.c |   2 +-
  drivers/i2c/soft_i2c.c           | 418 
-----------------------------------------------------------------------------------------------------------------------------------------------------
  7 files changed, 1 insertion(+), 540 deletions(-)


Azure build looks good:

https://dev.azure.com/hs0298/hs/_build/results?buildId=207&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-05-14 13:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 13:36 Heiko Schocher [this message]
2026-05-14 17:55 ` 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-07-09 15:24 Heiko Schocher
2026-07-10  1:11 ` 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=1f922957-e56d-1187-4441-e98e9f8fe25e@nabladev.com \
    --to=hs@nabladev.com \
    --cc=marek.vasut@mailbox.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox