From: Arjan van de Ven <arjanv@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
prism54-devel@prism54.org
Subject: Re: [PATCH 5/14 linux-2.6.7-rc1] prism54: new prism54 kernel compatibility
Date: Mon, 24 May 2004 10:53:50 +0200 [thread overview]
Message-ID: <1085388830.2780.9.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040524083220.GF3330@ruslug.rutgers.edu>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On Mon, 2004-05-24 at 10:32, Luis R. Rodriguez wrote:
> 2004-03-20 Margit Schubert-While <margitsw@t-online.de>
>
> * isl_38xx.[ch], isl_ioctl.c, islpci_dev.[ch], islpci_eth.c
> islpci_hotplug.c, islpci_mgt.[ch], oid_mgt.c: Adopt new
> prism54 kernel compatibility.
>
> * prismcompat.h, prismcompat24.h: New compatibility work
ewwww this makes the driver quite a bit less readable!
for example
-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)
- /* This is 2.6 specific, nicer, shorter, but not in 2.4 yet */
- DEFINE_WAIT(wait);
- prepare_to_wait(&priv->reset_done, &wait, TASK_UNINTERRUPTIBLE);
-#else
- DECLARE_WAITQUEUE(wait, current);
- set_current_state(TASK_UNINTERRUPTIBLE);
- add_wait_queue(&priv->reset_done, &wait);
-#endif
+ PRISM_DEFWAITQ(priv->reset_done, wait)
why not just make a DEFINE_WAIT() and prepare_to_wait() macro for 2.4
instead ?? so that you can just have the 2.6 version in the code and do
2.4 compat in a clean header, as opposed to fouling up the entire driver
with it.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-24 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 8:32 Luis R. Rodriguez
2004-05-24 8:53 ` Arjan van de Ven [this message]
2004-05-28 22:15 ` [Prism54-devel] " Luis R. Rodriguez
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=1085388830.2780.9.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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®