linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd@lists.infradead.org,
	David Woodhouse <dwmw2@infradead.org>,
	John Ogness <john.ogness@linutronix.de>
Subject: Re: Pull request: i.MX nand driver updates
Date: Sun, 29 Aug 2010 14:59:39 +0300	[thread overview]
Message-ID: <1283083179.2131.33.camel@brekeke> (raw)
In-Reply-To: <20100827105538.GB1473@pengutronix.de>

On Fri, 2010-08-27 at 12:55 +0200, Sascha Hauer wrote:
> > > are available in the git repository at:
> > >   git://git.pengutronix.de/git/imx/linux-2.6.git mtd-imx-nand
> > > 
> > > John Ogness (2):
> > >       mxc_nand: Do not do byte accesses to the NFC buffer.
> > >       mxc_nand: remove unused variables.
> > > 
> > > Sascha Hauer (10):
> > >       mxc_nand: remove 0xe00 offset from registers
> > >       mxc_nand: rework get_dev_status
> > >       mxc_nand: make some internally used functions overwriteable
> > >       mxc_nand: factor out a check_int function
> > >       mxc_nand: add V1_V2 namespace to registers
> > >       mxc_nand: support 8bit ecc
> > >       mxc_nand: fix correct_data function
> > >       mxc_nand: Add v3 (i.MX51) Support
> > >       mxc_nand: do not depend on disabling the irq in the interrupt handler
> > >       mxc_nand: configure pages per block for v2 controller
> > 
> > Um, that repo seems to be based on something earlier than 2.6.36-rc1.
> > And the real -rc1 already contains most of those commits.
> > 
> > I think there are four commits which aren't already included. Of those,
> > at least one looks like a bug fix which needs to go into 2.6.36. What
> > about the others?
> 
> The patch from John Ogness is a bug fix. 'configure pages per block for
> v2 controller' can be considered a bug fix since before this patch we
> relied on some register bits being set correctly by the bootloader.
> One patch can wait for the next merge window I think.
> I updated the branch to contain the following:

Not sure if David is confused or not, but I'm confused. Could you please
sent 2 separate pull requests: one pull request with stuff you want to
go to 2.6.36 (important fixes) and one request with 2.6.37 material.
Please, base both on the mtd-2.6.git tree. And make it clear in the
subject and the e-mail body which request contains what. This will make
things easier and will probably speed them up. And do not forget to
refresh the patches and add all Acks, if any :-)

Thanks!

-- 
Best Regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2010-08-29 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23  6:40 Pull request: i.MX nand driver updates Sascha Hauer
2010-08-26 23:37 ` David Woodhouse
2010-08-27 10:55   ` Sascha Hauer
2010-08-29 11:59     ` Artem Bityutskiy [this message]
2010-08-30 12:43       ` Pull request for 2.6.36 Sascha Hauer
2010-09-18 18:29         ` Artem Bityutskiy
2010-08-31 23:27     ` Pull request: i.MX nand driver updates Artem Bityutskiy
2010-09-01  5:36       ` Wolfram Sang

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=1283083179.2131.33.camel@brekeke \
    --to=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.hauer@pengutronix.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;
as well as URLs for NNTP newsgroup(s).