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: Wed, 01 Sep 2010 02:27:16 +0300 [thread overview]
Message-ID: <1283297236.2018.61.camel@brekeke> (raw)
In-Reply-To: <20100827105538.GB1473@pengutronix.de>
On Fri, 2010-08-27 at 12:55 +0200, Sascha Hauer wrote:
> 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:
I do not know what dwmw2 would answer, but I think it is wrong to send a
pull request based on something which is not in the tree you want to get
it. If dwmw2 pulls your tree, he will also pull all the other stuff, and
then get beaten by Linus for basing things on a random commit.
Anyway, I cherry-picked those 2 patches and put them to my
l2-mtd-2.6.git tree to the for-2.6.36 branch, and will bug dwmw2.
Please, send the rest of your stuff for 2.6.37 as well.
Also, please, use "mtd:" prefix for all your patches.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-08-31 23:27 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
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 ` Artem Bityutskiy [this message]
2010-09-01 5:36 ` Pull request: i.MX nand driver updates 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=1283297236.2018.61.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