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] NAND custodian (was Re: [PATCH v5 0/5] enable support for x16 NAND devices)
Date: Thu, 29 May 2014 07:28:06 +0200	[thread overview]
Message-ID: <5386C566.1010007@denx.de> (raw)
In-Reply-To: <20140528210014.GE1752@bill-the-cat>

Hello Tom,

Am 28.05.2014 23:00, schrieb Tom Rini:
> On Tue, May 27, 2014 at 12:21:21PM -0500, Scott Wood wrote:
>> On Tue, 2014-05-27 at 11:48 +0000, Gupta, Pekon wrote:
>>> Hello Scott, Tom,
>>>
>>>
>>>> From: Gupta, Pekon
>>>>
>>>> *changes v4 ->  v5*
>>>> [PATCH 1/5]<no change>
>>>> [PATCH 2/5] fixed compilation error for OMAP3 platforms
>>>> [PATCH 3/5]<no change>
>>>> [PATCH 4/5] dropped old [PATCH] mtd: nand: omap: add CONFIG_SYS_NAND_BUSWIDTH_16BIT to
>>>> indicate NAND device bus-width
>>>>             instead new [PATCH] mtd: nand: omap: add CONFIG_SYS_NAND_BUSWIDTH_16BIT to indicate
>>>> NAND device bus-width
>>>> [PATCH 5/5] additional cleanup in include/configs/cm_t35.h
>>>> Build tested for:      MAKEALL -s am33xx -s omap3 -s omap4 -s omap5
>>>> Rebased above series:  http://lists.denx.de/pipermail/u-boot/2014-April/177323.html
>>>>
>>>
>>> This series few other patch series are awaiting response from
>>> long time.
>>
>> Sorry for the delay -- I've been fairly busy, and don't usually get
>> around to processing U-Boot patches until after the merge window closes.
>> The IRC channel topic has been lying and saying the merge window is
>> still open (also, http://www.denx.de/wiki/U-Boot/ReleaseCycle says that
>> the merge window is open and will close in negative 24 days).
>
> Bah, I always forget to update those parts as well, beyond the actual
> releases...
>
>> Given that I don't do much with NAND myself these days, that the patch
>> volume is higher than when I started as NAND custodian, and that I now
>> have maintainership duties in Linux competing for my time, I'm wondering
>> if someone else (maybe you or Heiko?) wants to step into the NAND
>> custodian role.
>
> It's been a pleasure working with you.  Pekon? Heiko?  Either of you
> interested in this particular role?  Thanks!

I am not a NAND expert and I am little bit under water currently...
(but if nobody else volunteers I can try it ...)

Pekon?

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

  reply	other threads:[~2014-05-29  5:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 19:16 [U-Boot] [PATCH v5 0/5] enable support for x16 NAND devices Pekon Gupta
2014-05-05 19:16 ` [U-Boot] [PATCH v5 1/5] mtd: nand: don't use read_buf for 8-bit ONFI transfers Pekon Gupta
2014-06-06 21:54   ` [U-Boot] [U-Boot, v5, " Tom Rini
2014-05-05 19:16 ` [U-Boot] [PATCH v5 2/5] mtd: nand: force NAND_CMD_READID onto 8-bit bus Pekon Gupta
2014-06-06 21:54   ` [U-Boot] [U-Boot, v5, " Tom Rini
2014-05-05 19:16 ` [U-Boot] [PATCH v5 3/5] mtd: nand: fix GET/SET_FEATURES address on 16-bit devices Pekon Gupta
2014-06-06 21:54   ` [U-Boot] [U-Boot, v5, " Tom Rini
2014-05-05 19:16 ` [U-Boot] [PATCH v5 4/5] mtd: nand: omap: add CONFIG_SYS_NAND_BUSWIDTH_16BIT to indicate NAND device bus-width Pekon Gupta
2014-06-06 21:54   ` [U-Boot] [U-Boot, v5, " Tom Rini
2014-05-05 19:16 ` [U-Boot] [PATCH v5 5/5] omap3: remove remnant macros GPMC_NAND_ECC_LP_x8_LAYOUT and GPMC_NAND_ECC_LP_x16_LAYOUT Pekon Gupta
2014-06-06 21:54   ` [U-Boot] [U-Boot, v5, " Tom Rini
2014-05-27 11:48 ` [U-Boot] [PATCH v5 0/5] enable support for x16 NAND devices Gupta, Pekon
2014-05-27 17:21   ` [U-Boot] NAND custodian (was Re: [PATCH v5 0/5] enable support for x16 NAND devices) Scott Wood
2014-05-28 21:00     ` Tom Rini
2014-05-29  5:28       ` Heiko Schocher [this message]
2014-05-30  4:54         ` Gupta, Pekon

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=5386C566.1010007@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