public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: balrogg@gmail.com
Cc: Linux-OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: Palm Tungsten E board update
Date: Fri, 29 Sep 2006 14:07:58 +0300	[thread overview]
Message-ID: <20060929110757.GD19674@atomide.com> (raw)
In-Reply-To: <fb249edb0609281322u45c15f32wf62a92940aa6eab0@mail.gmail.com>

* andrzej zaborowski <balrog@zabor.org> [060928 23:22]:
> On 28/09/06, Tony Lindgren <tony@atomide.com> wrote:
> >* andrzej zaborowski <balrog@zabor.org> [060923 13:45]:
> >> General update of the board file for Palm Tungsten E. Registers the
> >> platform devices contained in the PDA (ROM chip, keypad, infra-red)
> >> and updates the configuration for USB and MMC, whose config values
> >> were previously guessed in most cases due to lack of documentation
> >> (and now are confirmed by a number of users). Macros for GPIO pins are
> >> moved to a file in include/asm-arm/arch-omap.
> >>
> >> Signed-off-by: Andrzej Zaborowski <balrog@zabor.org>
> >
> >Pushing today.
> 
> Many thanks.
> One thing though: the patch added a new file at
> include/asm-arm/arch-omap/board-palmte.h which didn't get merged and
> include/asm-arm/arch-omap/hardware.h now tries to #include the file.
> Can you add this header? (the attached diff contains this file alone)

Sorry, looks like I forgot to run git status again to see new files..

I'll revert and reapply your patch, that way the original patch will go
upstream.

Regards,

Tony

      reply	other threads:[~2006-09-29 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 10:39 [PATCH] ARM: OMAP: Palm Tungsten E board update andrzej zaborowski
2006-09-28 14:04 ` Tony Lindgren
2006-09-28 20:22   ` andrzej zaborowski
2006-09-29 11:07     ` tony [this message]

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=20060929110757.GD19674@atomide.com \
    --to=tony@atomide.com \
    --cc=balrogg@gmail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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