From: Simon Schwarz <simonschwarzcor@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V0] omap-common: move early UART clock setup to s_init
Date: Thu, 28 Jul 2011 16:49:08 +0200 [thread overview]
Message-ID: <4E3176E4.4080907@gmail.com> (raw)
In-Reply-To: <20110728130420.1A42F15794D5@gemini.denx.de>
Dear Wolfgang Denk,
On 07/28/2011 03:04 PM, Wolfgang Denk wrote:
> Dear Simon Schwarz,
>
> In message<1311844938-17278-2-git-send-email-simonschwarzcor@gmail.com> you wrote:
>> Moves the early UART clock setup setup_clocks_for_console() from
>> preloader_console_init() to s_init() of OMAP4.
>>
>> Signed-off-by: Simon Schwarz<simonschwarzcor@gmail.com>
>> ---
>> arch/arm/cpu/armv7/omap-common/spl.c | 1 -
>> arch/arm/cpu/armv7/omap4/board.c | 1 +
>> 2 files changed, 1 insertions(+), 1 deletions(-)
>
> I'm unhappy about the subject. not to mention again that you posted
> another (empty) patch with basicly the same subject line, but you say
> "omap-common:" in the subject, while the code looks to be OMAP4
> specific? This is kind of misleading.
>
Reason: omap-common because it is a omap-common change - the omap4 part
is just to fix it up for the SOC which is using it already.
So maybe deleting setup_clocks_for_console() would have been a better
subject, sorry.
> Best regards,
>
> Wolfgang Denk
>
Regards
Simon Schwarz
next prev parent reply other threads:[~2011-07-28 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 9:22 [U-Boot] [PATCH V0] omap-common: move early UART clock setup to board.c Simon Schwarz
2011-07-28 9:22 ` [U-Boot] [PATCH V0] omap-common: move early UART clock setup to s_init Simon Schwarz
2011-07-28 9:44 ` Andreas Bießmann
2011-07-29 12:51 ` Simon Schwarz
2011-07-28 13:04 ` Wolfgang Denk
2011-07-28 14:49 ` Simon Schwarz [this message]
2011-07-28 13:02 ` [U-Boot] [PATCH V0] omap-common: move early UART clock setup to board.c Wolfgang Denk
2011-07-28 14:53 ` Simon Schwarz
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=4E3176E4.4080907@gmail.com \
--to=simonschwarzcor@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.