From: dwmw2@infradead.org (David Woodhouse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/20] mtd: pxa3xx_nand: remove the flash info in driver structure
Date: Mon, 24 May 2010 10:45:05 +0100 [thread overview]
Message-ID: <1274694305.20576.2854.camel@macbook.infradead.org> (raw)
In-Reply-To: <AANLkTil9Toz4DU7YJ2B3Qtw3S1LCr90R7tlri7KC_NCC@mail.gmail.com>
On Mon, 2010-05-24 at 09:41 +0100, Lei Wen wrote:
> For this patch set change the original c file greatly, more than half
> of original code is changed,
> I cannot create a patch for each change. (If so, this patch set would
> grow to be a very large one. Maybe 30+?)
Yes you can -- large patch sets are fine. If email becomes cumbersome,
feel free to just publish it as a git tree. Once Mike approves I can
pull from it.
Let me have a SSH public key if you want to be able to publish a git
tree on git.infradead.org.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse at intel.com Intel Corporation
prev parent reply other threads:[~2010-05-24 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 6:13 [PATCH 03/20] mtd: pxa3xx_nand: remove the flash info in driver structure Haojian Zhuang
2010-05-24 7:25 ` Mike Rapoport
2010-05-24 8:41 ` Lei Wen
2010-05-24 9:45 ` David Woodhouse [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=1274694305.20576.2854.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).