From: Luca Ceresoli <luca.ceresoli@comelit.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] omap: gpio: Use generic API (instead of custom)
Date: Wed, 07 Sep 2011 11:24:04 +0200 [thread overview]
Message-ID: <4E673834.3020209@comelit.it> (raw)
In-Reply-To: <1315254528-8644-1-git-send-email-premi@ti.com>
Hi Sanjeev,
Sanjeev Premi wrote:
> The OMAP boards use a custom api for GPIO operations. While
> it works, it doesn't help when when we don't know existence
> of the customization.
...
> Changes since RFC[1]:
> 1) While the original RFC was based against the master of
> u-boot.git. This series is based against master of
> u-boot-arm.git
This patchset does not apply on top of current -arm master:
commit 1052ea04d60de953f8355eab0e39336974283304
Author: Sanjeev Premi <premi@ti.com>
Date: Mon Sep 5 00:25:53 2011 +0000
omap3: beagle: Fix build warning
With this message:
Applying: omap: gpio: Use generic API
error: patch failed: arch/arm/cpu/armv7/omap-common/gpio.c:151
error: arch/arm/cpu/armv7/omap-common/gpio.c: patch does not apply
error: patch failed: arch/arm/include/asm/omap_gpio.h:49
error: arch/arm/include/asm/omap_gpio.h: patch does not apply
Patch failed at 0001 omap: gpio: Use generic API
I'm afraid think you need another rebase.
Luca
next prev parent reply other threads:[~2011-09-07 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 20:28 [U-Boot] [PATCH 0/3] omap: gpio: Use generic API (instead of custom) Sanjeev Premi
2011-09-05 20:28 ` [U-Boot] [PATCH 1/3] omap: gpio: Use generic API Sanjeev Premi
2011-09-05 20:28 ` [U-Boot] [PATCH 2/3] omap: gpio: generic changes after changing API Sanjeev Premi
2011-09-05 20:28 ` [U-Boot] [PATCH 3/3] omap: gpio: Adapt board files to use generic API Sanjeev Premi
2011-09-05 20:46 ` [U-Boot] [PATCH 0/3] omap: gpio: Use generic API (instead of custom) Paulraj, Sandeep
2011-09-07 9:24 ` Luca Ceresoli [this message]
2011-09-07 9:39 ` Premi, Sanjeev
2011-09-07 9:48 ` Premi, Sanjeev
2011-09-08 12:51 ` Luca Ceresoli
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=4E673834.3020209@comelit.it \
--to=luca.ceresoli@comelit.it \
--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.