public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MAINTAINERS: add me as a maintainer of MTD
Date: Mon, 10 Nov 2014 08:32:19 +0100	[thread overview]
Message-ID: <54606A03.2090405@denx.de> (raw)
In-Reply-To: <CAD6G_RTa6cAmMUpK7JSQaZjRKomE4WO38G0ENQVswqzjtji32w@mail.gmail.com>

Hello Jagan,

Am 10.11.2014 07:38, schrieb Jagan Teki:
> On 10 November 2014 11:45, Heiko Schocher <hs@denx.de> wrote:
>> Add MAINTAINERS and doc/git-mailrc entry.
>>
>> Signed-off-by: Heiko Schocher <hs@denx.de>
>>
>> ---
>> as discussed this step here and there first of all with Scott Wood
>> for example here:
>> http://lists.denx.de/pipermail/u-boot/2014-August/186005.html
>>
>> I am now ready for taking over the ownership for MTD ...
>>
>> Scott guesses he could continue with NAND custodianship, thanks!
>> So no need for taking this into the MTD custodianship ... puuh ;-)
>>
>> @all: Please send me a list of pending patches, so I can go through
>>        them, thanks!
>>
>> Changes in v2:
>> add comment from Jagan Teki and Masahiro Yamada:
>> correct files entry in MAINTAINERS
>>
>>   MAINTAINERS    | 8 ++++++++
>>   doc/git-mailrc | 1 +
>>   2 files changed, 9 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 4e2f8a9..2ac55f8 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -258,6 +258,14 @@ S: Maintained
>>   T:     git git://git.denx.de/u-boot-mmc.git
>>   F:     drivers/mmc/
>>
>> +MTD
>> +M:     Heiko Schocher <hs@denx.de>
>> +S:     Maintained
>> +T:     git git://git.denx.de/u-boot-mtd.git
>> +F:     drivers/mtd/
>> +F:     include/linux/mtd/
>> +F:     include/mtd/
>> +
>
> This approach, I feel it's sounds not good to me.
> [1] as per my comments, it's good to add the maintainers who  belongs to

Hups... sorry. Seems I missed this EMail ...

> drivers/mtd as "MTD" maintainer so-that it is more defined way for any one
> in opensource to understand it - Linux is operating same i guess.

I could not parse you here ...

Looking in linux MAINTAINERS:

MEMORY TECHNOLOGY DEVICES (MTD)
M:      David Woodhouse <dwmw2@infradead.org>
M:      Brian Norris <computersforpeace@gmail.com>
L:      linux-mtd at lists.infradead.org
W:      http://www.linux-mtd.infradead.org/
Q:      http://patchwork.ozlabs.org/project/linux-mtd/list/
T:      git git://git.infradead.org/linux-mtd.git
S:      Maintained
F:      drivers/mtd/
F:      include/linux/mtd/
F:      include/uapi/mtd/
[...]
ONENAND FLASH DRIVER
M:      Kyungmin Park <kyungmin.park@samsung.com>
L:      linux-mtd at lists.infradead.org
S:      Maintained
F:      drivers/mtd/onenand/
F:      include/linux/mtd/onenand*.h
[...]
PHRAM MTD DRIVER
M:      Joern Engel <joern@lazybastard.org>
L:      linux-mtd at lists.infradead.org
S:      Maintained
F:      drivers/mtd/devices/phram.c
...
and a lot more ...

So where is the difference? The mtd mailinglist? I am sure
we do not want to introduce a seperate mailinglist...

I do not want to maintain your parts!

> Comments?

@Kyungmin Park: Could you comment here too, espacially for ubi/ubifs
                 IIRC I see no comments for the "MTD/UBI/UBIFS sync with
                 Linux 3.14" patches from me ... do you have longer time
                 for maintaining this?

                 There are also patches (some here for example which are
                 pending, and seeing no comments from you ...)

                 for example 2 examples from me:
                 [U-Boot] mtd, ubi: errormessage handling
                 http://patchwork.ozlabs.org/patch/405259/

                 [U-Boot,v2] ubi: enable error reporting in initialization
                 http://patchwork.ozlabs.org/patch/407136/
bye,
Heiko

> [1] http://u-boot.10912.n7.nabble.com/PATCH-MAINTAINERS-add-me-as-a-maintainer-of-MTD-td194237.html#a194619
>
>>   OPENRISC
>>   M:     Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
>>   S:     Maintained
>> diff --git a/doc/git-mailrc b/doc/git-mailrc
>> index ad22763..166fe37 100644
>> --- a/doc/git-mailrc
>> +++ b/doc/git-mailrc
>> @@ -116,6 +116,7 @@ alias fdt            uboot, sjg
>>   alias i2c            uboot, hs
>>   alias kconfig        uboot, masahiro
>>   alias mmc            uboot, panto
>> +alias mtd            uboot, hs
>>   alias nand           uboot, scottwood
>>   alias net            uboot, jhersh
>>   alias spi           uboot, jagan
>> --
>> 1.8.3.1
>>
>
> thanks!
>

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2014-11-10  7:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10  6:15 [U-Boot] [PATCH] MAINTAINERS: add me as a maintainer of MTD Heiko Schocher
2014-11-10  6:38 ` Jagan Teki
2014-11-10  7:32   ` Heiko Schocher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-31 10:26 Heiko Schocher
2014-10-31 10:43 ` Jagan Teki
2014-10-31 11:44   ` Wolfgang Denk
2014-10-31 12:29     ` Masahiro Yamada
2014-10-31 12:46       ` Heiko Schocher
2014-10-31 12:49         ` Stefan Roese
2014-10-31 12:48       ` Jagan Teki
2014-11-03 21:34 ` Scott Wood
2014-11-04 21:49   ` Jagan Teki
2014-11-05  7:08   ` Heiko Schocher
2014-11-06 20:43     ` Scott Wood

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=54606A03.2090405@denx.de \
    --to=hs@denx.de \
    --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