public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix warnings while compiling net/net.c for MPC8610HPCD board
Date: Wed, 30 Apr 2008 13:13:26 -0500	[thread overview]
Message-ID: <4818B6C6.20701@freescale.com> (raw)
In-Reply-To: <48188C90.8080409@freescale.com>

Timur Tabi wrote:
> Kumar Gala wrote:
> 
>> nothing against this patch, but should we change MPC8610HPCD to use - 
>> Os like everyone else?
> 
> Beats me.  git-blame points to Jon, so he'll have to tell you where the original
> config.mk came from.

Bah.  There is, let's see.... exactly one commit for that file:

    % git log board/freescale/mpc8610hpcd/config.mk
    commit 3dd2db53ceb0dff80f25c2a07f83f29b907b403e
    Author: Jon Loeliger <jdl@freescale.com>
    Date:   Tue Oct 16 13:54:01 2007 -0500

        Initial mpc8610hpcd board files.

        Signed-off-by: Ed Swarthout <Ed.Swarthout@freescale.com>
        Signed-off-by: Mahesh Jade <mahesh.jade@freescale.com>
        Signed-off-by: Jason Jin <Jason.jin@freescale.com>
        Signed-off-by: Jon Loeliger <jdl@freescale.com>

So, I'm guessing, it came from the Ed.  That is, it came that way
from the Day One.  So there.

jdl

  reply	other threads:[~2008-04-30 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 15:25 [U-Boot-Users] MPC8610HPCD build warnings Wolfgang Denk
2008-04-30 11:34 ` [U-Boot-Users] [PATCH] Fix warnings while compiling net/net.c for MPC8610HPCD board Anatolij Gustschin
2008-04-30 14:24   ` Kumar Gala
2008-04-30 14:39     ` Anatolij Gustschin
2008-04-30 15:13     ` Timur Tabi
2008-04-30 18:13       ` Jon Loeliger [this message]
2008-04-30 19:19         ` Timur Tabi
2008-04-30 15:38   ` Scott Wood
2008-04-30 20:31   ` Wolfgang Denk

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=4818B6C6.20701@freescale.com \
    --to=jdl@freescale.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