From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mxs_nand: Fix ECC strength for NAND flash with OOB size of 224
Date: Wed, 11 Sep 2013 09:24:34 +0200 [thread overview]
Message-ID: <52301AB2.6040704@denx.de> (raw)
In-Reply-To: <1378843872.12204.334.camel@snotra.buserror.net>
Hi Scott,
On 10/09/2013 22:11, Scott Wood wrote:
> Sure.
>
> Acked-by: Scott Wood <scottwood@freescale.com>
>
> 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. 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.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-09-11 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 14:51 [U-Boot] [PATCH] mxs_nand: Fix ECC strength for NAND flash with OOB size of 224 Elie De Brauwer
2013-09-10 17:02 ` Stefano Babic
2013-09-10 20:11 ` Scott Wood
2013-09-11 7:24 ` Stefano Babic [this message]
2013-09-11 16:53 ` 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=52301AB2.6040704@denx.de \
--to=sbabic@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