From: Rene Herman <rene.herman@keyaccess.nl>
To: trenn@suse.de
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
"yakui.zhao" <yakui.zhao@intel.com>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/3] PNP cleanups - Unify the pnp macros to access resources in the pnp resource table
Date: Tue, 20 Nov 2007 11:17:03 +0100 [thread overview]
Message-ID: <4742B41F.4000605@keyaccess.nl> (raw)
In-Reply-To: <1195552283.23700.166.camel@queen.suse.de>
On 20-11-07 10:51, Thomas Renninger wrote:
> Unify the pnp macros to access resources in the pnp resource table
>
> port, mem, dma and irq resource macros are now all used in the same
> way. This is the basis (or makes it at least easier) for changing how
> the resources are allocated for memory optimizations.
>
> Signed-off-by: Thomas Renninger <trenn@suse.de>
Acked-by: Rene Herman <rene.herman@gmail.com>
as identity transformation again.
Andrew Morton wrote:
> Normally when I get a big tree-wide patch like this I'll just drop the
> hunks which get rejects so that the patch doesn't screw up other people's
> trees if I merge first.
>
>
>> >
>> > Index: linux-2.6.24-rc2/include/linux/pnp.h
>> > ===================================================================
>> > --- linux-2.6.24-rc2.orig/include/linux/pnp.h
>> > +++ linux-2.6.24-rc2/include/linux/pnp.h
>> > @@ -55,7 +55,6 @@ struct pnp_dev;
>> > (pnp_mem_end((dev),(bar)) - \
>> > pnp_mem_start((dev),(bar)) + 1))
>> >
>> > -#define pnp_irq(dev,bar) ((dev)->res.irq_resource[(bar)].start)
>> > #define pnp_irq_start(dev,bar) ((dev)->res.irq_resource[(bar)].start)
>> > #define pnp_irq_end(dev,bar) ((dev)->res.irq_resource[(bar)].end)
>> > #define pnp_irq_flags(dev,bar) ((dev)->res.irq_resource[(bar)].flags)
>> > @@ -63,7 +62,6 @@ struct pnp_dev;
>> > ((pnp_irq_flags((dev),(bar)) & (IORESOURCE_IRQ | IORESOURCE_UNSET)) \
>> > == IORESOURCE_IRQ)
>> >
>> > -#define pnp_dma(dev,bar) ((dev)->res.dma_resource[(bar)].start)
>
> But if I do that, we'll get build breakage.
>
> And we'll break any files which you missed in the conversion, or which
> people currently have queued in the subsystem trees, or which people are
> maintaining out-of-tree.
>
> Hence I'd suggest that we retain the above as back-compatibility wrappers
> for a while.
And Shaohua Li wrote:
> patches are great. I have a minor comment. Keep pnp_irq and pnp_dma and
> define them as pnp_irq_start and pnp_dma_start. pnp_irq_start and
> pnp_dma_start is a little confusing from a pnp driver point of view.
Rene.
next prev parent reply other threads:[~2007-11-20 10:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 9:51 [PATCH 2/3] PNP cleanups - Unify the pnp macros to access resources in the pnp resource table Thomas Renninger
2007-11-20 10:17 ` Rene Herman [this message]
2007-11-20 12:31 ` Alan Cox
2007-11-20 14:19 ` Thomas Renninger
2007-11-20 14:31 ` Rene Herman
2007-11-20 14:31 ` Rene Herman
2007-11-20 16:48 ` Thomas Renninger
2007-11-21 9:53 ` Takashi Iwai
2007-11-21 9:53 ` [alsa-devel] " Takashi Iwai
2007-11-27 16:34 ` Thomas Renninger
2007-11-27 16:34 ` [alsa-devel] " Thomas Renninger
2007-11-27 16:52 ` Rene Herman
2007-11-27 16:52 ` [alsa-devel] " Rene Herman
2007-11-20 15:14 ` Alan Cox
2007-11-20 18:59 ` Andi Kleen
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=4742B41F.4000605@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=trenn@suse.de \
--cc=yakui.zhao@intel.com \
/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.