From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] mtd: add writebufsize field to mtd_info struct
Date: Tue, 01 Feb 2011 13:18:34 +0100 [thread overview]
Message-ID: <4D47FA1A.4000605@keymile.com> (raw)
In-Reply-To: <201102011028.09264.sr@denx.de>
Hi Stefan,
Stefan Roese wrote:
>
>> as I told in another mail, the min I/O size adaption patch leads to
>> incompatibilites for the UBIFS and therefore the similar patch in linux
>> kernel was reverted. But anyway the first five patches in the patch serie
>> are already part of the mtd layer of the linux kernel.
>>
>> So the patches 1-5 of this series can also be committed to u-boot. Whats
>> your opinion?
>
> I have no problems with applying patches 1-5. But they have been
> submitted after the merge window was closed, so they will not make it
> into the next release.
>
> I'm volunteering to push those patches into "next" (once its available)
> via one of my git repositories (UBI/UBIFS or CFI) if nobody else objects.
>
Ok, thanks.
Regards
Holger
prev parent reply other threads:[~2011-02-01 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 16:17 [U-Boot] [PATCH 1/6] mtd: add writebufsize field to mtd_info struct Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 2/6] cfi_mtd: add writebufsize initialization Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 3/6] mtd, nand: add mtd->writebufsize initialization Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 4/6] mtd, onenand: add mtd writebufsize initialization Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 5/6] mtd: initialize writebufsize in the MTD object of a partition Holger Brunck
2011-01-20 16:17 ` [U-Boot] [PATCH 6/6] UBI: use mtd->writebufsize to set minimal I/O unit size Holger Brunck
2011-01-27 16:18 ` [U-Boot] [PATCH 1/6] mtd: add writebufsize field to mtd_info struct Detlev Zundel
2011-02-01 8:26 ` Holger Brunck
2011-02-01 9:28 ` Stefan Roese
2011-02-01 12:18 ` Holger Brunck [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=4D47FA1A.4000605@keymile.com \
--to=holger.brunck@keymile.com \
--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