From: Linus Walleij <linus.ml.walleij-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linus Walleij
<linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Subject: Re: [PATCH 1/1] MFD: Add U300 AB3100 core support v3
Date: Wed, 20 May 2009 10:36:22 +0200 [thread overview]
Message-ID: <63386a3d0905200136i64bde4acw8944443a005f5d30@mail.gmail.com> (raw)
In-Reply-To: <20090519230601.GF23114-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
Thanks Ben, v4 due soon..
2009/5/20 Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>:
>> +#define AB3100_DEVICE(devname, devid, regstart, regend) \
>> +static struct resource ab3100_##devname##_resource[] = { \
>> + { \
>> + .start = regstart, \
>> + .end = regend, \
>> + .flags = IORESOURCE_IO, \
>> + } \
>
> is IORESOURCE_IO a good idea here, we may need to add some form of
> flag to say 'generic data' and for the driver core to not try and
> register it with any of the ioport or iomem structures.
I'll remove it for the time being, it's not used currently anyway.
Yell if you want me to create a patch to include/linux/platform_devices.h
for this too...
>> + {
>> + .id = 0xc8,
>> + .name = "P2B/R2B"
>> + },
>
> doing }, { would makes these shorter still.
Yeah CodingStyle actually say so if I read it closely, I'll fix.
Yours,
Linus Walleij
next prev parent reply other threads:[~2009-05-20 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 14:36 [PATCH 1/1] MFD: Add U300 AB3100 core support v3 Linus Walleij
[not found] ` <63386a3d0905190736q574d0379hb529aaa105aa36f3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-19 23:06 ` Ben Dooks
[not found] ` <20090519230601.GF23114-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-05-20 8:36 ` Linus Walleij [this message]
2009-06-19 8:42 ` Linus Walleij
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=63386a3d0905200136i64bde4acw8944443a005f5d30@mail.gmail.com \
--to=linus.ml.walleij-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).