public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kirkwood: implement kw_sdram_bs_set()
Date: Thu, 5 Jul 2012 13:02:22 +0200	[thread overview]
Message-ID: <20120705130222.7c403fdf@aari01-12> (raw)
In-Reply-To: <4FF57328.2030504@keymile.com>

Hi Gerlando,

On Thu, 05 Jul 2012 12:57:44 +0200, Gerlando Falauto
<gerlando.falauto@keymile.com> wrote:
> Hi Albert,
> 
> On 07/05/2012 12:39 PM, Albert ARIBAUD wrote:
> > Hi Gerlando,
> >
> > On Fri, 29 Jun 2012 13:37:54 +0200, Gerlando Falauto
> > <gerlando.falauto@keymile.com>  wrote:
> >> Some boards might be equipped with different SDRAM configurations.
> >> When that is the case, CPU CS Window Size Register (CS[0]n Size)
> >> should be set to the biggest value through board.cfg file; then its
> >> value can be fixed at runtime according to the detected SDRAM size.
> >>
> >> Therefore, implement kw_sdram_bs_set(), to be called for instance
> >> within board_early_init_f().
> >>
> [...]
> >
> > I don't like isolated patches that seem to create dead code. I know
> > here it is not the goal, of course; so why not submit a two-patch
> > series, providing both the new code *and* a use for it?
> 
> You're absolutely right.
> But mine was more of an interruption/suggestion throughout the 
> discussion between Marek and Prafulla... I just didn't want to take 
> credit for someone else's code, or create any conflicts with it.

Understood. Next time, please just add [RFC] in the subject, so that
the patch is not considered for inclusion.

> I figured it might be quicker (and more fair) that way, perhaps with 
> Marek resubmitting it within his own series, or SoB-ing it, because
> in fact mine is just a refactoring of his idea...
> I can of course submit the two-patch series for our boards, if that's
> OK with Marek.

That's to be sorted between Marek and you. :)

> Thanks,
> Gerlando

Amicalement,
-- 
Albert.

  reply	other threads:[~2012-07-05 11:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 18:49 [U-Boot] [PATCH 1/2] KW: Move the memory register definitions into kirkwood.h Marek Vasut
2012-06-26 18:49 ` [U-Boot] [PATCH 2/2] Kirkwood: Add support for Ka-Ro TK71 Marek Vasut
2012-06-27 12:02   ` [U-Boot] [PATCH 2/2 V2] " Marek Vasut
2012-07-03 11:43     ` Prafulla Wadaskar
2012-07-03 11:56     ` Prafulla Wadaskar
2012-07-03 12:08     ` Prafulla Wadaskar
2012-07-03 12:23       ` Marek Vasut
2012-07-03 12:27     ` [U-Boot] [PATCH V3 2/2] " Marek Vasut
2012-07-03 12:44       ` Prafulla Wadaskar
2012-07-03 12:51         ` Marek Vasut
2012-07-03 13:00           ` Prafulla Wadaskar
2012-07-03 13:03             ` Marek Vasut
2012-07-03 13:02       ` [U-Boot] [PATCH 2/2 V4] " Marek Vasut
2012-07-03 13:12         ` Prafulla Wadaskar
2012-06-29 10:02 ` [U-Boot] [PATCH 1/2] KW: Move the memory register definitions into kirkwood.h Gerlando Falauto
2012-06-29 10:08   ` Marek Vasut
2012-06-29 10:27     ` Gerlando Falauto
2012-06-29 10:51       ` Marek Vasut
2012-06-29 11:37 ` [U-Boot] [PATCH] kirkwood: implement kw_sdram_bs_set() Gerlando Falauto
2012-07-05 10:39   ` Albert ARIBAUD
2012-07-05 10:57     ` Gerlando Falauto
2012-07-05 11:02       ` Albert ARIBAUD [this message]
2012-07-05 12:16         ` Prafulla Wadaskar

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=20120705130222.7c403fdf@aari01-12 \
    --to=albert.u.boot@aribaud.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