From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Yaffs] yaffs2 u-boot patching support
Date: Mon, 23 Apr 2012 08:18:58 -0700 [thread overview]
Message-ID: <4F9572E2.5040308@ti.com> (raw)
In-Reply-To: <201204230823.28547.manningc2@actrix.gen.nz>
On 04/22/2012 01:23 PM, Charles Manning wrote:
> On Friday 20 April 2012 09:40:50 Tom Rini wrote:
>> On Mon, Apr 16, 2012 at 04:32:07PM +1200, Charles Manning wrote:
>>> Hello ubooters and yaffsers
>>>
>>> I was commissioned to refresh yaffs2 in u-boot and add a mechanism to
>>> support dynamic yaffs partition set up (way simpler than screwing around
>>> with mtd part) and manual configuration.
>>>
>>> Rather than do this as a once off, I set this scripting up so that this
>>> can be done at any time (painlessly I hope) to bring in the fresh code
>>> (as per Linux patching).
>>
>> Just to put this out there, if you're not submitting patches to get the
>> code into git, should the current support in-tree be removed?
>
> I think it is worth having yaffs in the main code base, but not the old stuff.
>
> The primary reason to have a "patch-in" script is to allow people to refresh
> the yaffs they are using in a pretty painless way.
OK, but why not just update mainline? When you posted the original
message, the next branch of master was open. Today master is open. I'm
pretty sure that a pull request from the yaffs2 maintainers to update
the codebase would be accepted if it's self contained to fs/yaffs2 and
reviewed if it touches stuff outside. This isn't the old days... Thanks!
--
Tom
next prev parent reply other threads:[~2012-04-23 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 4:32 [U-Boot] yaffs2 u-boot patching support Charles Manning
2012-04-19 21:40 ` Tom Rini
2012-04-22 20:23 ` [U-Boot] [Yaffs] " Charles Manning
2012-04-23 15:18 ` Tom Rini [this message]
2012-04-23 15:33 ` Stefano Babic
2012-04-25 20:43 ` Charles Manning
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=4F9572E2.5040308@ti.com \
--to=trini@ti.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