From: Tom Rini <trini@konsulko.com>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: U-Boot Mailing List <U-Boot@lists.denx.de>,
John Keeping <john@metanate.com>,
Jae hoon Chung <jh80.chung@gmail.com>
Subject: Re: [GIT PULL] Please pull u-boot-pmic master
Date: Tue, 31 Jan 2023 22:33:11 -0500 [thread overview]
Message-ID: <Y9nddwTF1lWcih8x@bill-the-cat> (raw)
In-Reply-To: <8196de61-9d1a-efbe-068d-66db880ab272@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On Wed, Feb 01, 2023 at 08:17:42AM +0900, Jaehoon Chung wrote:
> 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/14954
>
>
> The following changes since commit 30db474704405be823259851cbb76fa05366c8af:
>
> Prepare v2023.04-rc1 (2023-01-30 15:36:45 -0500)
>
> 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 519fa7aa252789677939f0bd991bf26a4fe469ec:
>
> power: act8846_pmic: fix number of registers (2023-01-31 22:05:03 +0900)
>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-02-01 3:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230131231742epcas1p4eba2ff2ec3ad1ecebccbd804ec41231a@epcas1p4.samsung.com>
2023-01-31 23:17 ` [GIT PULL] Please pull u-boot-pmic master Jaehoon Chung
2023-02-01 3:33 ` Tom Rini [this message]
[not found] <CGME20240429082059epcas1p1f35772730ea8c9b8caf558bc360152c2@epcas1p1.samsung.com>
2024-04-29 8:20 ` Jaehoon Chung
2024-04-29 16:49 ` Tom Rini
[not found] <CGME20221227011937epcas1p2935b0b4debd26f20c00d892980522ca1@epcas1p2.samsung.com>
2022-12-27 1:19 ` Jaehoon Chung
2022-12-27 15:10 ` Tom Rini
[not found] <CGME20221026062213epcas1p180d065e38e24ed89f8d8bc9adb248604@epcas1p1.samsung.com>
2022-10-26 6:22 ` Jaehoon Chung
2022-10-26 15:25 ` 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=Y9nddwTF1lWcih8x@bill-the-cat \
--to=trini@konsulko.com \
--cc=U-Boot@lists.denx.de \
--cc=jh80.chung@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=john@metanate.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 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.