From: Jaehoon Chung <jh80.chung@samsung.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Peng Fan <peng.fan@nxp.com>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] MAINTAINER, git-mailrc: Update the mmc maintainer
Date: Mon, 14 Jun 2021 09:22:15 +0900 [thread overview]
Message-ID: <583ef332-159e-427e-b9ce-a3b878c8493d@samsung.com> (raw)
In-Reply-To: <CAEUhbmV2j3MCMBL4CZh8f2rVG1eANHM08Eg-rdr5PBfjMAL+WA@mail.gmail.com>
Hi Bin,
On 6/14/21 8:57 AM, Bin Meng wrote:
> Hi Jaehoon,
>
> On Mon, Jun 14, 2021 at 7:33 AM Jaehoon Chung <jh80.chung@samsung.com> wrote:
>>
>> Update to me as co-maintainer with Peng.
>> Additionally, fix the alias in git-mailrc.
>>
>> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
>> ---
>> MAINTAINERS | 1 +
>> doc/git-mailrc | 6 +++---
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 86ff5e04a62b..a9257cde4df2 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -882,6 +882,7 @@ F: arch/mips/dts/mrvl,cn73xx.dtsi
>>
>> MMC
>> M: Peng Fan <peng.fan@nxp.com>
>> +M: Jaehoon Chung <jh80.chung@samsung.com>
>> S: Maintained
>> T: git https://protect2.fireeye.com/v1/url?k=79b7d831-262ce129-79b6537e-0cc47a314e9a-cdf3442d5d2979bd&q=1&e=64a4c301-fdd1-4fc7-9483-a67d605ed544&u=https%3A%2F%2Fsource.denx.de%2Fu-boot%2Fcustodians%2Fu-boot-mmc.git
>> F: drivers/mmc/
>> diff --git a/doc/git-mailrc b/doc/git-mailrc
>> index 34f936f4d83c..2627edb09ac0 100644
>> --- a/doc/git-mailrc
>> +++ b/doc/git-mailrc
>> @@ -25,7 +25,7 @@ alias dinh Dinh Nguyen <dinguyen@kernel.org>
>> alias hs Heiko Schocher <hs@denx.de>
>> alias freenix Peng Fan <peng.fan@nxp.com>
>> alias iwamatsu Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
>> -alias jaehoon Jaehoon Chung <jh80.chung@samsung.com>
>> +alias Jaehoon Jaehoon Chung <jh80.chung@samsung.com>
>
> I am not sure why this has to be capital letter? Did it break anything?
In patchwork, my account is Jaehoon, not jaehoon.
So I have changed to same alias as my patchwork account.
If there is no problem, i will not modify this.
Best Regards,
Jaehoon Chung
>
>> alias jagan Jagan Teki <jagan@amarulasolutions.com>
>> alias jhersh Joe Hershberger <joe.hershberger@ni.com>
>> alias kevery Kever Yang <kever.yang@rock-chips.com>
>> @@ -119,7 +119,7 @@ alias kerneldoc uboot, marex
>> alias fdt uboot, sjg
>> alias i2c uboot, hs
>> alias kconfig uboot, masahiro
>> -alias mmc uboot, freenix
>> +alias mmc uboot, freenix, Jaehoon
>> alias nand uboot
>> alias net uboot, jhersh
>> alias phy uboot, jhersh
>> @@ -131,4 +131,4 @@ alias xhci uboot, bmeng
>> alias video uboot, ag
>> alias patman uboot, sjg
>> alias buildman uboot, sjg
>> -alias pmic uboot, jaehoon
>> +alias pmic uboot, Jaehoon
>>
>
> Regards,
> Bin
>
next prev parent reply other threads:[~2021-06-14 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210613233259epcas1p3a41583053c68564def2c7a3cef55a298@epcas1p3.samsung.com>
2021-06-13 23:33 ` [PATCH] MAINTAINER, git-mailrc: Update the mmc maintainer Jaehoon Chung
2021-06-13 23:57 ` Bin Meng
2021-06-14 0:22 ` Jaehoon Chung [this message]
2021-06-14 1:12 ` Bin Meng
2021-06-14 1:27 ` Jaehoon Chung
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=583ef332-159e-427e-b9ce-a3b878c8493d@samsung.com \
--to=jh80.chung@samsung.com \
--cc=bmeng.cn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).