From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PULL-REQ] MTD update
Date: Sun, 30 Dec 2012 08:24:00 +0530 [thread overview]
Message-ID: <50DFACC8.3020700@gmail.com> (raw)
In-Reply-To: <20121228135953.GA14134@bill-the-cat>
On 12/28/2012 7:29 PM, Tom Rini wrote:
> On Fri, Dec 28, 2012 at 07:17:42AM -0500, Sergey Lapin wrote:
>
>> Hi, all!
>>
>> As I failed to submit 250KB patch to the list
>> I will send this pull request
>>
>> This patch is not for inclusion yet.
>> This patch is just update of u-boot MTD with
>> Linux kernel's MTD v3.8-rc.
>
> First, while I appreciate the effort, I'd rather us sync with v3.7
> release rather than the in-flux v3.8. Second, can you please look at
> the archives about how we've done these re-syncs before? I really don't
> want to take a single giant patch and we're usually able to break this
> up into chunks. Thanks!
Can someone point to the exact thread where such discussion has happened
before?
The re-sync has to happen addressing the bisect-ability as well.
Already there was a discussion on syncing the UBI layer. So, if some
ideas are thrown, it would be beneficial for both MTD and UBI sync.
Thanks,
Vikram
next prev parent reply other threads:[~2012-12-30 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 12:17 [U-Boot] [RFC][PULL-REQ] MTD update Sergey Lapin
2012-12-28 13:51 ` Wolfgang Denk
2012-12-28 15:07 ` Sergey Lapin
2012-12-28 15:14 ` Wolfgang Denk
2012-12-28 13:59 ` Tom Rini
2012-12-29 20:54 ` Sergey Lapin
2012-12-29 21:03 ` Marek Vasut
2012-12-29 21:52 ` Wolfgang Denk
2012-12-29 22:20 ` Sergey Lapin
2012-12-29 23:13 ` Sergey Lapin
2012-12-29 23:21 ` Marek Vasut
2012-12-29 23:33 ` Wolfgang Denk
2012-12-30 0:35 ` Sergey Lapin
2012-12-30 2:54 ` Vikram Narayanan [this message]
2013-01-02 15:33 ` Tom Rini
2013-01-03 3:22 ` Scott Wood
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=50DFACC8.3020700@gmail.com \
--to=vikram186@gmail.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