From: Jeff Garzik <jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Andrew Grover
<andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Code obfuscation in acpi
Date: Sat, 18 Jan 2003 17:32:10 -0500 [thread overview]
Message-ID: <20030118223210.GA31860@gtf.org> (raw)
In-Reply-To: <20030118213134.GA8968-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
On Sat, Jan 18, 2003 at 10:31:34PM +0100, Pavel Machek wrote:
>
> #define acpi_driver_data(d) ((d)->driver_data)
>
> ... very nice for obfuscating code ...
sysfs-based buses use <foo>_{get,set}_drvdata, which looks exactly the
same as this here.
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>,
Andrew Grover <andrew.grover@intel.com>
Subject: Re: Code obfuscation in acpi
Date: Sat, 18 Jan 2003 17:32:10 -0500 [thread overview]
Message-ID: <20030118223210.GA31860@gtf.org> (raw)
In-Reply-To: <20030118213134.GA8968@elf.ucw.cz>
On Sat, Jan 18, 2003 at 10:31:34PM +0100, Pavel Machek wrote:
>
> #define acpi_driver_data(d) ((d)->driver_data)
>
> ... very nice for obfuscating code ...
sysfs-based buses use <foo>_{get,set}_drvdata, which looks exactly the
same as this here.
Jeff
next prev parent reply other threads:[~2003-01-18 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 21:31 Code obfuscation in acpi Pavel Machek
2003-01-18 21:31 ` Pavel Machek
[not found] ` <20030118213134.GA8968-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-01-18 22:32 ` Jeff Garzik [this message]
2003-01-18 22:32 ` Jeff Garzik
[not found] ` <20030118223210.GA31860-bB7D8CACdjo@public.gmane.org>
2003-01-18 22:39 ` Pavel Machek
2003-01-18 22:39 ` Pavel Machek
2003-01-20 1:44 ` Rik van Riel
2003-01-20 1:44 ` Rik van Riel
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=20030118223210.GA31860@gtf.org \
--to=jgarzik-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.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 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.