From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] The omap3 L2 cache enable/disable function to omap3 dependent code
Date: Mon, 01 Jun 2009 18:46:21 +0200 [thread overview]
Message-ID: <4A2405DD.7040106@googlemail.com> (raw)
In-Reply-To: <20090601105427.47afbbc8.kim.phillips@freescale.com>
Kim Phillips wrote:
> On Mon, 1 Jun 2009 19:14:49 +0900
> "Kim, Heung Jun" <riverful@gmail.com> wrote:
>
>> CC: Dirk Behme <dirk.behme@googlemail.com>
>> Signed-off-by: HeungJun, Kim <riverful.kim@samsung.com>
>>
>> ---
>>
>> The L2 cache enable/disable function in the cpu/arm_cortexa8/cpu.c moved
>> to cpu/arm_cortexa8/omap3/cache.c.
>>
>> This patches fixes the First issue in the following
>>
>> http://lists.denx.de/pipermail/u-boot/2009-May/053433.html
>>
>> The Second issue is fixed by
>>
>> http://lists.denx.de/pipermail/u-boot/2009-May/053490.html
>>
>
> Hi Riverful,
>
> 1. the patch title is missing the verb 'move'
> 2. your signoff is in the correct location, however the commit message
> is not. It belongs above the line with the '---'.
> 3. while making backreferences by pointing to messages in the list
> archive is cool, they don't stand the test of time - the URL may one
> day cease to exist. So it is better to either reference a commitish in
> the repository itself, or simply restate/copy the original data.
As long as references to the mailing list archive are in patch comment
(below --- as they are here) and don't go into git I think it's fine
to use them.
Best regards
Dirk
next prev parent reply other threads:[~2009-06-01 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:14 [U-Boot] [PATCH] The omap3 L2 cache enable/disable function to omap3 dependent code Kim, Heung Jun
2009-06-01 15:54 ` Kim Phillips
2009-06-01 16:08 ` Kim, Heung Jun
2009-06-01 16:24 ` Kim Phillips
2009-06-01 16:46 ` Dirk Behme [this message]
2009-06-01 17:49 ` Kim Phillips
-- strict thread matches above, loose matches on Subject: below --
2009-06-01 8:21 Kim, Heung Jun
2009-06-01 8:36 ` Kim, Heung Jun
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=4A2405DD.7040106@googlemail.com \
--to=dirk.behme@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox