From: Stephan Linz <linz@li-pro.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] microblaze: Enable ubi support
Date: Tue, 26 Jun 2012 18:56:49 +0200 [thread overview]
Message-ID: <1340729809.2767.52.camel@keto> (raw)
In-Reply-To: <CAHTX3d+t_GTwNfeDsXy1FTq3L9xCuP_cibRaQvxAGk9VxCASww@mail.gmail.com>
Am Dienstag, den 26.06.2012, 10:52 +0200 schrieb Michal Simek:
> 2012/6/25 Stephan Linz <linz@li-pro.net>:
> > Am Montag, den 25.06.2012, 09:22 +0200 schrieb Wolfgang Denk:
> >> Dear Michal Simek,
> >>
> >> In message <4FE7F154.80406@monstr.eu> you wrote:
> >> > On 06/21/2012 09:42 PM, Stephan Linz wrote:
> >> > > To save memory the UBIFS is disabled by default.
> >> > >
> >> > > The original patch was introdused with commit:
> >> > > 0114da7b06bd47b7f5c3f20a152dd11903b38fba
> >> >
> >> > This say nothing to me.
> >> > Format is Patch name and when sha1.
> >> >
> >> > Where is this patch? I can't see it in mainline repository?
> >>
> >> Correct. This commit does not exist in mainline.
> >
> > Yes, the commit was newer merged into mainline and lives for more than
> > one year in Microblaze custodian repo:
> >
> > http://git.denx.de/?p=u-boot/u-boot-microblaze.git;a=commitdiff;h=0114da7b06bd47b7f5c3f20a152dd11903b38fba
>
> I have there two branches - master and uboot. uboot follows mainline
> branch and master contain one your patch
> which was merged to mainline.
> That link is correct but it points to nonexisting branch.
> That patch was definitely there but that branch was delete quite some time ago.
Yes, it was in the net (?) branch that was deleted sometime.
>
> Wolfgang: How to run git-gc on this repository?
>
> I am ok to add this to mainline. Please add that two patches together
> and resubmit.
I'll do so (three patches -- see my other comment).
> Also I would prefer to define SYS_MALLOC_LEN based on SIZE.
> It means for example
> #define CONFIG_SYS_MALLOC_LEN (SIZE *2)
> or similar.
OK, I'll evaluate the best factor for this multiplication.
br,
Stephan
next prev parent reply other threads:[~2012-06-26 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 19:42 [U-Boot] [PATCH 1/2] microblaze: avoid compile error on systems without cfi flash Stephan Linz
2012-06-21 19:42 ` [U-Boot] [PATCH 2/2] microblaze: Enable ubi support Stephan Linz
2012-06-25 5:04 ` Michal Simek
2012-06-25 7:22 ` Wolfgang Denk
2012-06-25 17:08 ` Stephan Linz
2012-06-26 8:52 ` Michal Simek
2012-06-26 16:56 ` Stephan Linz [this message]
2012-06-25 4:55 ` [U-Boot] [PATCH 1/2] microblaze: avoid compile error on systems without cfi flash Michal Simek
2012-06-25 17:08 ` Stephan Linz
2012-06-26 8:56 ` Michal Simek
2012-06-26 16:56 ` Stephan Linz
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=1340729809.2767.52.camel@keto \
--to=linz@li-pro.net \
--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