From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Tegra2: Change mach-type to MACH_TYPE_SEABOARD due to mach-types.h update
Date: Thu, 24 Mar 2011 15:27:04 +0100 [thread overview]
Message-ID: <4D8B54B8.6020708@free.fr> (raw)
In-Reply-To: <AANLkTimERMevkRv+hkAwxRgjAf6TEHmQOGK2WzfPSnGG@mail.gmail.com>
Le 22/03/2011 20:27, Tom Warren a ?crit :
> Albert,
>
> On Wed, Feb 23, 2011 at 1:45 PM, Albert ARIBAUD<albert.aribaud@free.fr> wrote:
>> Le 23/02/2011 21:03, Tom Warren a ?crit :
>>>
>>> OK, I'm an idiot. I see now that I needed to add -n to format-patch to
>>> add the numbering to the [PATCH] header.
>>>
>>> Sorry for the noise - resending now with the corrected patchset.
>>>
>>> Tom
>>
>> Actually, for a single patch, you don't need to generate numbers, nor a
>> cover letter (the 0/N message).
> Is the current patch OK as is? It's a simple one-line change.
I guess so. As soon as I get confirmation from Wolfgang that board
patches can go through any tree, I'll apply it as a bugfix to master.
> Thanks,
> Tom
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-03-24 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 19:54 [U-Boot] [PATCH] Tegra2 Seaboard: Fix mach_type to match mach-type.h update Tom Warren
2011-02-23 19:54 ` [U-Boot] [PATCH] arm: Tegra2: Change mach-type to MACH_TYPE_SEABOARD due to mach-types.h update Tom Warren
2011-02-23 20:03 ` Tom Warren
2011-02-23 20:45 ` Albert ARIBAUD
2011-03-22 19:27 ` Tom Warren
2011-03-24 14:27 ` Albert ARIBAUD [this message]
2011-03-24 15:08 ` Tom Warren
2011-03-27 16:22 ` Albert ARIBAUD
2011-03-28 16:27 ` Tom Warren
2011-03-24 19:42 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2011-02-23 16:43 [U-Boot] [PATCH] Tegra2 Seaboard: Fix mach_type to match mach-type.h update Tom Warren
2011-02-23 16:43 ` [U-Boot] [PATCH] arm: Tegra2: Change mach-type to MACH_TYPE_SEABOARD due to mach-types.h update Tom Warren
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=4D8B54B8.6020708@free.fr \
--to=albert.aribaud@free.fr \
--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