From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Kirkwood: add Marvell Sheevaplug gpio support
Date: Mon, 29 Jun 2009 11:15:28 +0200 [thread overview]
Message-ID: <200906291115.29032.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E201D90657B6@SC-VEXCH1.marvell.com>
Am Montag 29 Juni 2009 10:15:22 schrieb Prafulla Wadaskar:
>
> > -----Original Message-----
> > From: Dieter Kiermaier [mailto:dk-arm-linux at gmx.de]
> > Sent: Monday, June 29, 2009 1:33 PM
> > To: u-boot at lists.denx.de
> > Cc: Prafulla Wadaskar
> > Subject: [PATCH] Kirkwood: add Marvell Sheevaplug gpio support
> >
> > Hi List,
> >
> > this if my first patch which goes to the wild. So please
> > don't be croos with me if I made some stupid thing :) Any
> > comments or feedback would be very welcome!
> >
> > Is it common that the patch writer gives his Signed-off-by or
> > who is responsible for that?
> >
> > Cheers,
> > Dieter
> >
> >
> > From e89ebedf1528e821e504c91af802687efb21533b Mon Sep 17 00:00:00 2001
> > From: Dieter Kiermaier <dk-arm-linux@gmx.de>
> > Date: Fri, 26 Jun 2009 14:45:13 +0200
> > Subject: [PATCH] Kirkwood: add Marvell Sheevaplug gpio support
> Signed-off-by is MUST
>
> >
> > ---
> > board/Marvell/sheevaplug/sheevaplug.c | 1 +
> > cpu/arm926ejs/kirkwood/Makefile | 1 +
> > cpu/arm926ejs/kirkwood/gpio.c | 144
> > +++++++++++++++++++++++++++++++++
> > include/asm-arm/arch-kirkwood/gpio.h | 43 ++++++++++
> Spilt this patch into two, 1. gpio support for Kirkwood SOC and 2. Sheevaplug updates
> Move gpio stuff to drivers/gpio/
>
Is it ok to leave gpio.h file in include/asm-arm/arch-kirkwood/ ?
Thanks,
Dieter
next prev parent reply other threads:[~2009-06-29 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <73173D32E9439E4ABB5151606C3E19E201D90657B6@SC-VEXCH1.marvell.com>
2009-06-29 8:23 ` [U-Boot] [PATCH] Kirkwood: add Marvell Sheevaplug gpio support Dieter Kiermaier
2009-06-29 9:15 ` Dieter Kiermaier [this message]
2009-06-29 8:02 Dieter Kiermaier
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=200906291115.29032.dk-arm-linux@gmx.de \
--to=dk-arm-linux@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox