From: Tom Rini <trini@konsulko.com>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: U-Boot Mailing List <U-Boot@lists.denx.de>,
Loic Poulain <loic.poulain@linaro.org>,
Marek Vasut <marex@denx.de>, Stefan Roese <sr@denx.de>,
Jae hoon Chung <jh80.chung@gmail.com>
Subject: Re: [GIT PULL] Please pull u-boot-mmc master
Date: Fri, 10 Mar 2023 10:44:12 -0500 [thread overview]
Message-ID: <20230310154412.GH3041508@bill-the-cat> (raw)
In-Reply-To: <2319d02f-5cbb-7844-7d57-c38242601479@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On Fri, Mar 10, 2023 at 01:22:15PM +0900, Jaehoon Chung wrote:
> Dear Tom,
>
>
> Please pull u-boot-mmc master into u-boot master branch.
> If there is any problem, let me know, plz.
At this point in the cycle I have to ask, are these all fixes of
specific issues? If not, I'd rather take this to -next. Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-03-10 15:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230310042215epcas1p1fdf2d3566134769ce7a384e02555b72f@epcas1p1.samsung.com>
2023-03-10 4:22 ` [GIT PULL] Please pull u-boot-mmc master Jaehoon Chung
2023-03-10 15:44 ` Tom Rini [this message]
2023-03-10 16:28 ` Marek Vasut
2023-03-10 16:30 ` Stefan Roese
2023-03-10 18:08 ` Tom Rini
2023-03-13 5:26 ` Jaehoon Chung
2023-03-12 23:06 ` Jaehoon Chung
[not found] <CGME20240426103830epcas1p3720a09dd50c8ef3d16de0a6ff2ff514b@epcas1p3.samsung.com>
2024-04-26 10:38 ` Jaehoon Chung
2024-04-26 15:51 ` Tom Rini
2024-04-29 20:39 ` Judith Mendez
2024-04-29 22:34 ` Jaehoon Chung
2024-04-30 7:42 ` Francesco Dolcini
2024-05-01 7:30 ` Greg Malysa
2024-05-02 2:40 ` Greg Malysa
2024-05-02 14:17 ` Judith Mendez
[not found] <CGME20240415095231epcas1p4106945fe2de51e77e1fd60684c3c83bb@epcas1p4.samsung.com>
2024-04-15 9:52 ` Jaehoon Chung
2024-04-16 0:35 ` Tom Rini
[not found] <CGME20231101075631epcas1p319becae866c164fd73339181486f8f35@epcas1p3.samsung.com>
2023-11-01 7:56 ` Jaehoon Chung
2023-11-01 14:47 ` Tom Rini
[not found] <CGME20230718074927epcas1p35e9551400a04bf405b78288e2a75bd85@epcas1p3.samsung.com>
2023-07-18 7:49 ` Jaehoon Chung
2023-07-19 14:46 ` Tom Rini
[not found] <CGME20230704012927epcas1p105b12a861e9d2503989486c42fbdf964@epcas1p1.samsung.com>
2023-07-04 1:29 ` Jaehoon Chung
2023-07-06 7:16 ` Jaehoon Chung
[not found] <CGME20230410101856epcas1p31eeb4d987e1323b270e82f40d67f81aa@epcas1p3.samsung.com>
2023-04-10 10:18 ` Jaehoon Chung
2023-04-10 14:37 ` Tom Rini
[not found] <CGME20230131233835epcas1p4dce463a1db46e3ef773ca560fd305af8@epcas1p4.samsung.com>
2023-01-31 23:38 ` Jaehoon Chung
2023-02-01 3:33 ` Tom Rini
[not found] <CGME20221025005507epcas1p131b66b1491086a79905fc40491104ba3@epcas1p1.samsung.com>
2022-10-25 0:55 ` Jaehoon Chung
2022-10-25 13:53 ` Tom Rini
[not found] <CGME20220727080103epcas1p4c3103d75001a8582f37066f46e2b4209@epcas1p4.samsung.com>
2022-07-27 8:01 ` Jaehoon Chung
2022-07-27 13:05 ` Tom Rini
[not found] <CGME20220615225725epcas1p20fb187b0577d3951ce329ac864763cac@epcas1p2.samsung.com>
2022-06-15 22:57 ` Jaehoon Chung
2022-06-16 19:17 ` Tom Rini
[not found] <CGME20220316103012epcas1p326fb2f912a3a467259138214e7d56c42@epcas1p3.samsung.com>
2022-03-16 10:30 ` Jaehoon Chung
2022-03-16 14:48 ` Tom Rini
[not found] <CGME20220209010344epcas1p29487c28bee1a49b78058de7f8114b197@epcas1p2.samsung.com>
2022-02-09 1:04 ` Jaehoon Chung
2022-02-10 12:36 ` Tom Rini
[not found] <CGME20220112023702epcas1p3ac13f4eab0415c6f04da0703e870fecf@epcas1p3.samsung.com>
2022-01-12 2:37 ` Jaehoon Chung
2022-01-12 15:38 ` Tom Rini
[not found] <CGME20211029105118epcas1p11d7a7c3ba1799d374e6e39f95f9e50e1@epcas1p1.samsung.com>
2021-10-29 10:52 ` Jaehoon Chung
2021-10-29 17:28 ` 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=20230310154412.GH3041508@bill-the-cat \
--to=trini@konsulko.com \
--cc=U-Boot@lists.denx.de \
--cc=jh80.chung@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=loic.poulain@linaro.org \
--cc=marex@denx.de \
--cc=sr@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.