public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
	"ezequiel.garcia@free-electrons.com"
	<ezequiel.garcia@free-electrons.com>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v4 0/4] optimize and clean-up of OMAP NAND and ELM driver
Date: Thu, 5 Dec 2013 01:05:23 -0800	[thread overview]
Message-ID: <20131205090523.GD4636@norris.computersforpeace.net> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EA51F9E@DBDE04.ent.ti.com>

On Thu, Dec 05, 2013 at 08:54:34AM +0000, Pekon Gupta wrote:
> >From: Brian Norris [mailto:computersforpeace@gmail.com]
> >
> >I'm sorry to delay this long, but this patch series is still rather
> >impenetrable for a third-party reader, and so I really can't give my sign-off.
> >
> >For one, you don't give very good patch titles; 3 of the 4 have "optimize" in
> >the title, when in fact that "optimize" does not mean anything about
> >optimization, but rather, "unification", "consolidation", "cleanup", or
> >something else entirely, depending on which part of the patch you're talking
> >about... which brings me to the next point:
> >
> I think with all sorts of patches, I feel I have completely re-written the
> omap nand driver. After this series and one more, I think there is hardly
> any line in omap2.c which is not touched. So, I'm run-out of good titles :-)

I understand there is a lot of rewriting. The problem here is just that
you're doing too many things in a single patch.

> >Patches 1 and 4 are doing much more than one thing. Your commit messages
> >-- rather than describing succintly a single change being made -- are a
> >description of a list of things that you did, some of which are quite
> >independent.
> >
> Ok I'll first try to break each patch in smaller chunks..
> But this would bloat the number of patches, so I would break this series
> into multiple series, hope that's fine ?
>  - Patch series for chip->ecc.correct()
>  - Patch series for chip->ecc.calculate()
>  - Patch series for chip->ecc.hwctl()
>  - Patch series for ELM 

Hmm, if there are as many dependencies between patches as I expect, then
I think it's best to be a single series still. Too many patches is not
really a problem in itself, as long as the patches are reviewable
chunks.

> >If you need clarification on how you can best rework/resubmit this work,
> >please ask. I don't want this series to drag on to version 12+, so let's
> >focus on how to get this right now.
> >
> Agreed, thanks for feedback.
> I'll resubmit these patches breaking them into independent versions.
> Hopefully then it would be easy to review.

Ok, thanks for the effort.

Brian

      reply	other threads:[~2013-12-05  9:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 10:08 [PATCH v4 0/4] optimize and clean-up of OMAP NAND and ELM driver Pekon Gupta
2013-11-25 10:08 ` [PATCH v4 1/4] mtd: nand: omap: optimized chip->ecc.correct() for H/W ECC schemes Pekon Gupta
2013-11-25 10:08 ` [PATCH v4 2/4] mtd: nand: omap: optimize chip->ecc.calculate() " Pekon Gupta
2013-11-25 10:09 ` [PATCH v4 3/4] mtd: nand: omap: optimize chip->ecc.hwctl() " Pekon Gupta
2013-11-25 10:09 ` [PATCH v4 4/4] mtd: devices: elm: add checks ELM H/W constrains, driver code cleanup Pekon Gupta
2013-12-05  8:57   ` Brian Norris
2013-12-02 19:51 ` [PATCH v4 0/4] optimize and clean-up of OMAP NAND and ELM driver Gupta, Pekon
2013-12-05  8:31   ` Brian Norris
2013-12-05  8:54     ` Gupta, Pekon
2013-12-05  9:05       ` Brian Norris [this message]

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=20131205090523.GD4636@norris.computersforpeace.net \
    --to=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.com \
    /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