All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Enric Balletbo i Serra <eballetbo@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] omap3: Add minimal OMAP3 IGEP module support.
Date: Fri, 1 Oct 2010 16:19:47 -0700	[thread overview]
Message-ID: <20101001231947.GJ3117@atomide.com> (raw)
In-Reply-To: <1285971985-5662-1-git-send-email-eballetbo@gmail.com>

* Enric Balletbo i Serra <eballetbo@gmail.com> [101001 15:18]:
> The OMAP3 IGEP module is a low-power, high performance production-ready
> system-on-module (SOM) based on TI's OMAP3 family.

Looks OK to me, but also looks like you're missing the uncompress.h
DEBUG_LL/EARLY_PRINTK entry?

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap3: Add minimal OMAP3 IGEP module support.
Date: Fri, 1 Oct 2010 16:19:47 -0700	[thread overview]
Message-ID: <20101001231947.GJ3117@atomide.com> (raw)
In-Reply-To: <1285971985-5662-1-git-send-email-eballetbo@gmail.com>

* Enric Balletbo i Serra <eballetbo@gmail.com> [101001 15:18]:
> The OMAP3 IGEP module is a low-power, high performance production-ready
> system-on-module (SOM) based on TI's OMAP3 family.

Looks OK to me, but also looks like you're missing the uncompress.h
DEBUG_LL/EARLY_PRINTK entry?

Regards,

Tony

  reply	other threads:[~2010-10-01 23:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 22:26 [PATCH] omap3: Add minimal OMAP3 IGEP module support Enric Balletbo i Serra
2010-10-01 22:26 ` Enric Balletbo i Serra
2010-10-01 23:19 ` Tony Lindgren [this message]
2010-10-01 23:19   ` Tony Lindgren
2010-10-02  9:41   ` Enric Balletbò i Serra
2010-10-02  9:41     ` Enric Balletbò i Serra

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=20101001231947.GJ3117@atomide.com \
    --to=tony@atomide.com \
    --cc=eballetbo@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    /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.