U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: U-Boot Mailing List <U-Boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>,
	msuchanek@suse.de, John Keeping <john@metanate.com>,
	Jae hoon Chung <jh80.chung@gmail.com>
Subject: [GIT PULL] Please pull u-boot-pmic master
Date: Wed, 26 Oct 2022 15:22:12 +0900	[thread overview]
Message-ID: <ead2b409-1893-6ac7-2c3b-2e5f2183436d@samsung.com> (raw)
In-Reply-To: CGME20221026062213epcas1p180d065e38e24ed89f8d8bc9adb248604@epcas1p1.samsung.com

Dear Tom,


Please pull u-boot-pmic master into u-boot master branch.
If there is a problem, let me know, plz

Best Regards,
Jaehoon Chung

CI: https://source.denx.de/u-boot/custodians/u-boot-pmic/-/pipelines/13944

The following changes since commit f9d16f2c0daf68dcb963c08c927f5f0a07cf75e4:

  Merge https://source.denx.de/u-boot/custodians/u-boot-spi (2022-10-25 09:54:59 -0400)

are available in the Git repository at:

  git@source.denx.de:u-boot/custodians/u-boot-pmic.git master

for you to fetch changes up to 0b9186277a944dd7c34c5d01850fbe57b6bfa10a:

  power: fan53555: Fix missing newline in error message (2022-10-26 11:47:25 +0900)

----------------------------------------------------------------
John Keeping (1):
      power: regulator: fix autoset error handling

Michal Suchanek (1):
      power: fan53555: Fix missing newline in error message

 drivers/power/pmic/fan53555.c              | 2 +-
 drivers/power/regulator/regulator-uclass.c | 8 +++++++-
 2 files changed, 8 insertions(+), 2 deletions(-)

       reply	other threads:[~2022-10-26  6:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221026062213epcas1p180d065e38e24ed89f8d8bc9adb248604@epcas1p1.samsung.com>
2022-10-26  6:22 ` Jaehoon Chung [this message]
2022-10-26 15:25   ` [GIT PULL] Please pull u-boot-pmic master Tom Rini
     [not found] <CGME20250114015324epcas1p4c2c83151f7110658531d7ac9c5222630@epcas1p4.samsung.com>
2025-01-14  1:53 ` Jaehoon Chung
2025-01-15  1:13   ` Tom Rini
     [not found] <CGME20241205025813epcas1p48a97abeabb5fa0ca5ae22443963c9117@epcas1p4.samsung.com>
2024-12-05  2:58 ` Jaehoon Chung
2024-12-05 16:24   ` Tom Rini
     [not found] <CGME20240429082059epcas1p1f35772730ea8c9b8caf558bc360152c2@epcas1p1.samsung.com>
2024-04-29  8:20 ` Jaehoon Chung
2024-04-29 16:49   ` Tom Rini
     [not found] <CGME20230131231742epcas1p4eba2ff2ec3ad1ecebccbd804ec41231a@epcas1p4.samsung.com>
2023-01-31 23:17 ` Jaehoon Chung
2023-02-01  3:33   ` Tom Rini
     [not found] <CGME20221227011937epcas1p2935b0b4debd26f20c00d892980522ca1@epcas1p2.samsung.com>
2022-12-27  1:19 ` Jaehoon Chung
2022-12-27 15:10   ` Tom Rini
     [not found] <CGME20220727062516epcas1p2b317736d39786c2bee09b5e8f25dbd9f@epcas1p2.samsung.com>
2022-07-27  6:25 ` Jaehoon Chung
2022-07-27 13:05   ` Tom Rini
     [not found] <CGME20220615225940epcas1p425ee00e3f0a1a14ab0c65c91ba018c04@epcas1p4.samsung.com>
2022-06-15 22:59 ` Jaehoon Chung
2022-06-16 19:17   ` Tom Rini
     [not found] <CGME20220116231948epcas1p2d49e416fa19a42eb8062f6e35c2591fe@epcas1p2.samsung.com>
2022-01-16 23:20 ` Jaehoon Chung
2022-01-17 16:11   ` 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=ead2b409-1893-6ac7-2c3b-2e5f2183436d@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=U-Boot@lists.denx.de \
    --cc=jh80.chung@gmail.com \
    --cc=john@metanate.com \
    --cc=msuchanek@suse.de \
    --cc=trini@konsulko.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