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 1/3] PNP cleanups - Make use of pnp_{port,mem,irq,dma}_{start,end,flags} macros wherever possible
Date: Tue, 20 Nov 2007 11:16:35 +0100 [thread overview]
Message-ID: <4742B403.6060802@keyaccess.nl> (raw)
In-Reply-To: <1195552273.23700.164.camel@queen.suse.de>
On 20-11-07 10:51, Thomas Renninger wrote:
> Make use of pnp_{port,mem,irq,dma}_{start,end,flags} macros wherever possible
>
> The macros to access the resource table in pnp sublayer was not used
> consequently.
> This patch makes use of these macros instead of accessing the resource
> arrays directly.
>
> For dma and irq also pnp_{dma,irq}_{start,end} macros have been introduced
> to unify the access to the different resource types.
>
> The pnp_{irq,dma} macros has now the same functionality than the:
> pnp_{irq,dma}_start macros. This will be cleaned up by the next patch.
>
> Signed-off-by: Thomas Renninger <trenn@suse.de>
Earlier comments (in private mail):
>> - dev->res.port_resource[nport].start =
>> + pnp_port_start(dev, nport) =
>> simple_strtoul(buf, &buf, 0);
>> If I'm not mistaken, there's a standing fatwa on macros as lvalues.
>> Andrew?
>
> Andrew Morton wrote:
>
> Well, it's a pretty nasty thing to do, IMO. But given that we've already
> gone and done it I suppose the change is OK from a consistency POV.
Otherwise acked as identity transformation.
Acked-by: Rene Herman <rene.herman@gmail.com>
Rene.
next prev parent reply other threads:[~2007-11-20 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 9:51 [PATCH 1/3] PNP cleanups - Make use of pnp_{port,mem,irq,dma}_{start,end,flags} macros wherever possible Thomas Renninger
2007-11-20 10:16 ` Rene Herman [this message]
2007-11-20 12:32 ` Alan Cox
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=4742B403.6060802@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox