From: Scott Wood Date: Wed, 11 Sep 2013 11:53:28 -0500 Subject: [U-Boot] [PATCH] mxs_nand: Fix ECC strength for NAND flash with OOB size of 224 In-Reply-To: <52301AB2.6040704@denx.de> References: <1377355884-5920-1-git-send-email-eliedebrauwer@gmail.com> <522F50A6.20105@denx.de> <1378843872.12204.334.camel@snotra.buserror.net> <52301AB2.6040704@denx.de> Message-ID: <1378918408.12204.391.camel@snotra.buserror.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, 2013-09-11 at 09:24 +0200, Stefano Babic wrote: > Hi Scott, > > On 10/09/2013 22:11, Scott Wood wrote: > > Sure. > > > > Acked-by: Scott Wood > > > > I'm curious who's been doing these patchwork assignments and what > > they're basing it on. > > > > I think that everyone of us custodians has write rights to assign > patches. Personally, I check the list and I assign myself the i.MXes. > Surely there are a lot of unassigned patches, and someone tries to make > order - better there is who takes care of a patch as to let the patch > oblivious. Sure... Probably what prompted the comment more than this was when other people assign patches to me that aren't in the NAND code (e.g. UBI patches, or patches in arch/board code). Then I need to choose between just unassigning them, or figuring out who to assign them to, and I can't even see who assigned them to me to ask them about it. A log of patchwork updates would be nice. > However, this is an error-prone approach, and it should be > nice if there could be an automatic way to assign patches, maybe using > the subject. It'd be nice if the files touched could be used. -Scott