From: Ben Dooks <ben-linux@fluff.org>
To: Joonyoung Shim <jy0922.shim@samsung.com>
Cc: ben-linux@fluff.org, linux-samsung-soc@vger.kernel.org
Subject: Re: ARM: SAMSUNG: question about cfg_eint field of struct s3c_gpio_cfg
Date: Thu, 3 Jun 2010 01:51:03 +0100 [thread overview]
Message-ID: <20100603005103.GF30276@trinity.fluff.org> (raw)
In-Reply-To: <4C039BE4.3040904@samsung.com>
On Mon, May 31, 2010 at 08:22:12PM +0900, Joonyoung Shim wrote:
> Hi,
>
> There is cfg_eint field in struct s3c_gpio_cfg at
> arch/arm/plat-samsung/include/plat/gpio-cfg.h. I don't know the usage of
> cfg_eint. It isn't used anywhere or just assigned. Does it need really?
It was there for the interrupt code to configure the external-interrupt
information, but it was never used. It probably wants deleting if we can't
re-use it.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
prev parent reply other threads:[~2010-06-03 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 11:22 ARM: SAMSUNG: question about cfg_eint field of struct s3c_gpio_cfg Joonyoung Shim
2010-06-03 0:51 ` Ben Dooks [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=20100603005103.GF30276@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=jy0922.shim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
/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