All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo70@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] add mcf5307 support
Date: Wed, 10 Aug 2011 22:25:21 +0200	[thread overview]
Message-ID: <4E42E931.7080003@gmail.com> (raw)
In-Reply-To: <m27h6lm4ui.fsf@ohwell.denx.de>

Hi Detlev,

i don't have big experience with git, generally i use cvs/svn.

I am posting changes/additions i have here in my local tree, since i am not an u-boot developer i don't think i am allowed to commit anything in the server repository.

so "git format-patch -n --cover-letter"  don't give any output.





On 10/08/2011 21:41, Detlev Zundel wrote:
> Hi Angelo,
> 
>> Cpu architecture files.
>>
>> #       new file:   arch/m68k/cpu/mcf530x/Makefile
>> #       new file:   arch/m68k/cpu/mcf530x/config.mk
>> #       new file:   arch/m68k/cpu/mcf530x/cpu.c
>> #       new file:   arch/m68k/cpu/mcf530x/cpu.h
>> #       new file:   arch/m68k/cpu/mcf530x/cpu_init.c
>> #       new file:   arch/m68k/cpu/mcf530x/interrupts.c
>> #       new file:   arch/m68k/cpu/mcf530x/speed.c
>> #       new file:   arch/m68k/cpu/mcf530x/start.S
>>
>> Signed-off-by: Angelo Dureghello <sysamfw@gmail.com>
> 
> Which files are added is a detail already contained in the patch itself,
> it does not need to be included additionally.
> 
> To find out how other people handle commits, simply use "git log" in the
> u-boot directory and give some consideration to its output.
> 
> Cheers
>   Detlev
> 

  reply	other threads:[~2011-08-10 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 18:22 [U-Boot] [PATCH 1/3] add mcf5307 support Angelo Dureghello
2011-08-10 19:41 ` Detlev Zundel
2011-08-10 20:25   ` Angelo Dureghello [this message]
2011-08-10 20:58     ` Detlev Zundel

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=4E42E931.7080003@gmail.com \
    --to=angelo70@gmail.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.