From: "Magnus Damm" <magnus.damm@gmail.com>
To: "Ben Dooks" <ben-linux@fluff.org>
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
gregkh@suse.de, lethal@linux-sh.org, i2c@lm-sensors.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 02/05] resource: add resource_type() and IORESOURCE_TYPE_BITS
Date: Fri, 18 Jul 2008 17:24:59 +0900 [thread overview]
Message-ID: <aec7e5c30807180124j3623675fwaeedcaf23e4b0b05@mail.gmail.com> (raw)
In-Reply-To: <20080718075601.GL24620@fluff.org.uk>
On Fri, Jul 18, 2008 at 4:56 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> You are changing a simple test to a mask and compare, is anyone going
> to produce resources with an IORESOURCE_MEM and an IORESOURCE_IO
> together?
Actually, I'd like to replace the one-bit-per-type strategy with a
N-bit counter. But that is not very compatible with the case you are
pointing out. I'm not sure if that's a combination we really want to
support though. Both IRQ and DMA doesn't make much sense to me. =)
/ magnus
next prev parent reply other threads:[~2008-07-18 8:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 7:40 [PATCH 00/05] resource: type, size and IORESOURCE_CLK patches V2 Magnus Damm
2008-07-18 7:40 ` [PATCH 01/05] resource: add resource_size() Magnus Damm
2008-07-18 7:54 ` Ben Dooks
2008-07-18 7:40 ` [PATCH 02/05] resource: add resource_type() and IORESOURCE_TYPE_BITS Magnus Damm
2008-07-18 7:56 ` Ben Dooks
2008-07-18 8:24 ` Magnus Damm [this message]
2008-07-18 8:33 ` Ben Dooks
2008-07-18 9:05 ` Magnus Damm
2008-07-18 7:40 ` [PATCH 03/05] resource: add new IORESOURCE_CLK type V2 Magnus Damm
2008-07-18 7:53 ` [i2c] " Ben Dooks
2008-07-18 8:53 ` Magnus Damm
2008-07-18 7:40 ` [PATCH 04/05] i2c-sh_mobile: IORESOURCE_CLK support Magnus Damm
2008-07-18 8:04 ` Ben Dooks
2008-07-18 9:18 ` Magnus Damm
2008-08-13 5:54 ` [i2c] " Ben Dooks
2008-08-13 7:51 ` Russell King
2008-07-18 7:40 ` [PATCH 05/05] sh: add IORESOURCE_CLK to SuperH Mobile I2C platform data Magnus Damm
2008-07-18 23:36 ` Andrew Morton
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=aec7e5c30807180124j3623675fwaeedcaf23e4b0b05@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=gregkh@suse.de \
--cc=i2c@lm-sensors.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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
all inboxes | Powered by JetHome®