From: Marcel Holtmann <marcel@holtmann.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-pcmcia@lists.infradead.org, netdev@vger.kernel.org,
linux-bluetooth@vger.kernel.org, linux-ide@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-scsi@vger.kernel.org,
alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
Jiri Kosina <jkosina@suse.cz>, Karsten Keil <isdn@linux-pingi.de>
Subject: Re: [PATCH 13/13] pcmcia: rework the irq_req_t typedef
Date: Wed, 11 Nov 2009 21:46:03 +0100 [thread overview]
Message-ID: <1257972363.21467.7.camel@violet> (raw)
In-Reply-To: <1257971899-9274-13-git-send-email-linux@dominikbrodowski.net>
Hi Dominik,
> Most of the irq_req_t typedef'd struct can be re-worked quite
> easily:
>
> (1) IRQInfo2 was unused in any case, so drop it.
>
> (2) IRQInfo1 was used write-only, so drop it.
>
> (3) Instance (private data to be passed to the IRQ handler):
> Most PCMCIA drivers using pcmcia_request_irq() to actually
> register an IRQ handler set the "dev_id" to the same pointer
> as the "priv" pointer in struct pcmcia_device. Modify the two
> exceptions (ipwireless, ibmtr_cs) to also work this waym and
> set the IRQ handler's "dev_id" to p_dev->priv unconditionally.
>
> (4) Handler is to be of type irq_handler_t.
>
> (5) Handler != NULL already tells whether an IRQ handler is present.
> Therefore, we do not need the IRQ_HANDLER_PRESENT flag in
> irq_req_t.Attributes.
>
> CC: netdev@vger.kernel.org
> CC: linux-bluetooth@vger.kernel.org
> CC: linux-ide@vger.kernel.org
> CC: linux-wireless@vger.kernel.org
> CC: linux-scsi@vger.kernel.org
> CC: alsa-devel@alsa-project.org
> CC: Jaroslav Kysela <perex@perex.cz>
> CC: Jiri Kosina <jkosina@suse.cz>
> CC: Karsten Keil <isdn@linux-pingi.de>
> Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
> ---
> drivers/ata/pata_pcmcia.c | 1 -
> drivers/bluetooth/bluecard_cs.c | 4 +---
> drivers/bluetooth/bt3c_cs.c | 4 +---
> drivers/bluetooth/btuart_cs.c | 4 +---
> drivers/bluetooth/dtl1_cs.c | 4 +---
for the Bluetooth parts:
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
prev parent reply other threads:[~2009-11-11 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 20:33 [RFC] even more PCMCIA cleanup patches for 2.6.33 Dominik Brodowski
2009-11-11 20:38 ` [PATCH 06/13] pcmcia: Pass struct pcmcia_device to pcmcia_map_mem_page() Dominik Brodowski
2009-11-13 12:22 ` Karsten Keil
2009-11-11 20:38 ` [PATCH 11/13] pcmcia: pcmcia_request_window() doesn't need a pointer to a pointer Dominik Brodowski
2009-11-13 12:21 ` Karsten Keil
2009-11-11 20:38 ` [PATCH 12/13] pcmcia: remove deprecated handle_to_dev() macro Dominik Brodowski
2009-11-11 20:38 ` [PATCH 13/13] pcmcia: rework the irq_req_t typedef Dominik Brodowski
2009-11-11 20:46 ` Marcel Holtmann [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=1257972363.21467.7.camel@violet \
--to=marcel@holtmann.org \
--cc=alsa-devel@alsa-project.org \
--cc=isdn@linux-pingi.de \
--cc=jkosina@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=netdev@vger.kernel.org \
--cc=perex@perex.cz \
/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).