From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] asm-offsets: generate bd_t size
Date: Mon, 10 Jan 2011 08:50:25 +0100 [thread overview]
Message-ID: <4D2ABA41.7030805@monstr.eu> (raw)
In-Reply-To: <20110109170830.A2517127@gemini.denx.de>
Hi Wolfgang and Mike,
Wolfgang Denk wrote:
> Dear Mike Frysinger,
>
> In message <1293213443-11027-1-git-send-email-vapier@gentoo.org> you wrote:
>> Some ports set up the board info structure at the same time as the global
>> data structure, and largely keep them together. So generate a define for
>> the board info struct too.
>>
>> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
>> ---
>> lib/asm-offsets.c | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> Applied, thanks.
I am little bit confused.
1. Mike's patch has broken coding style in his patch ("space"+"space"15)
2. I sent that patch 3 days before Mike. (It is the longer story)
http://lists.denx.de/pipermail/u-boot/2010-December/084095.html
I like that the patch is in mainline tree because I need it for
Microblaze but I don't quite understand that you beat me about coding
style and then you apply patch which has broken coding style.
I don't care if that patch is Mike's or mine I would like to be sure
what are that acceptance rules.
Can you please tell me how this can happen?
Best regards,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2011-01-10 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 17:57 [U-Boot] [PATCH] asm-offsets: generate bd_t size Mike Frysinger
2011-01-09 17:08 ` Wolfgang Denk
2011-01-10 7:50 ` Michal Simek [this message]
2011-01-10 9:41 ` Mike Frysinger
2011-01-10 10:57 ` Wolfgang Denk
2011-01-10 15:57 ` Michal Simek
2011-01-10 10:46 ` Wolfgang Denk
2011-01-10 16:04 ` Michal Simek
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=4D2ABA41.7030805@monstr.eu \
--to=monstr@monstr.eu \
--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.