From: Vasily Khoruzhick <anarsoul@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Ben Dooks <ben-linux@fluff.org>,
"Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH RFC] h1940: use gpiolib for latch access
Date: Mon, 26 Jul 2010 08:40:35 +0300 [thread overview]
Message-ID: <201007260841.25560.anarsoul@gmail.com> (raw)
In-Reply-To: <20100725223521.GA14747@n2100.arm.linux.org.uk>
[-- Attachment #1: Type: Text/Plain, Size: 706 bytes --]
В сообщении от 26 июля 2010 01:35:21 автор Russell King - ARM Linux написал:
> On Sun, Jul 25, 2010 at 07:41:12PM +0300, Vasily Khoruzhick wrote:
> > diff --git a/arch/arm/mach-s3c2410/include/mach/h1940-latch.h
> > b/arch/arm/mach-s3c2410/include/mach/h1940-latch.h index
> > d8a8327..4607d5c 100644
> > --- a/arch/arm/mach-s3c2410/include/mach/h1940-latch.h
> > +++ b/arch/arm/mach-s3c2410/include/mach/h1940-latch.h
> > @@ -14,51 +14,30 @@
> >
> > #ifndef __ASM_ARCH_H1940_LATCH_H
> > #define __ASM_ARCH_H1940_LATCH_H
> >
> > +#include <mach/gpio.h>
>
> Would linux/gpio.h make more sense here?
Nope, mach/gpio.h is for S3C_GPIO_END
Regards
Vasily
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] h1940: use gpiolib for latch access
Date: Mon, 26 Jul 2010 08:40:35 +0300 [thread overview]
Message-ID: <201007260841.25560.anarsoul@gmail.com> (raw)
In-Reply-To: <20100725223521.GA14747@n2100.arm.linux.org.uk>
? ????????? ?? 26 ???? 2010 01:35:21 ????? Russell King - ARM Linux ???????:
> On Sun, Jul 25, 2010 at 07:41:12PM +0300, Vasily Khoruzhick wrote:
> > diff --git a/arch/arm/mach-s3c2410/include/mach/h1940-latch.h
> > b/arch/arm/mach-s3c2410/include/mach/h1940-latch.h index
> > d8a8327..4607d5c 100644
> > --- a/arch/arm/mach-s3c2410/include/mach/h1940-latch.h
> > +++ b/arch/arm/mach-s3c2410/include/mach/h1940-latch.h
> > @@ -14,51 +14,30 @@
> >
> > #ifndef __ASM_ARCH_H1940_LATCH_H
> > #define __ASM_ARCH_H1940_LATCH_H
> >
> > +#include <mach/gpio.h>
>
> Would linux/gpio.h make more sense here?
Nope, mach/gpio.h is for S3C_GPIO_END
Regards
Vasily
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100726/df34cbd1/attachment.sig>
next prev parent reply other threads:[~2010-07-26 5:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 16:41 [PATCH RFC] h1940: use gpiolib for latch access Vasily Khoruzhick
2010-07-25 16:41 ` Vasily Khoruzhick
2010-07-25 22:35 ` Russell King - ARM Linux
2010-07-25 22:35 ` Russell King - ARM Linux
2010-07-26 5:40 ` Vasily Khoruzhick [this message]
2010-07-26 5:40 ` Vasily Khoruzhick
2010-08-04 15:26 ` Ben Dooks
2010-08-04 15:26 ` Ben Dooks
2010-08-19 13:56 ` Vasily Khoruzhick
2010-08-19 13:56 ` Vasily Khoruzhick
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=201007260841.25560.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.