[U-Boot] NAND custodian (was Re: [PATCH v5 0/5] enable support for x16 NAND devices)

Scott Wood scottwood at freescale.com
Tue May 27 19:21:21 CEST 2014


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).

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.

-Scott




More information about the U-Boot mailing list