From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] fdt: Include arch specific gpio.h instead of asm-generic/gpio.h
Date: Fri, 10 Aug 2012 21:56:33 +0200 [thread overview]
Message-ID: <20120810215633.5a0127b3@wker> (raw)
In-Reply-To: <1342009598-19122-1-git-send-email-monstr@monstr.eu>
Hi,
On Wed, 11 Jul 2012 14:26:38 +0200
Michal Simek <monstr@monstr.eu> wrote:
> Include arch specific gpio.h instead of asm-generic/gpio.h
> because several architectures (Microblaze, Blackfin, Nios2, OpenRISC)
> define gpio functions in header file.
> asm-generic/gpio.h can be included in arch specific gpio.h
> (For example: ARM)
>
> Signed-off-by: Michal Simek <monstr@monstr.eu>
> CC: Simon Glass <sjg@chromium.org>
>
> ---
> v2: Use only arch specific gpio.h
> Remove commentary
> ---
> lib/fdtdec.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
applied to my staging branch, thanks!
Anatolij
prev parent reply other threads:[~2012-08-10 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 12:26 [U-Boot] [PATCH v2] fdt: Include arch specific gpio.h instead of asm-generic/gpio.h Michal Simek
2012-07-18 22:56 ` Mike Frysinger
2012-08-06 7:37 ` Michal Simek
2012-08-06 20:59 ` Simon Glass
2012-08-10 19:56 ` Anatolij Gustschin [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=20120810215633.5a0127b3@wker \
--to=agust@denx.de \
--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.