From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Eric Miao <eric.y.miao@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] Palm interrupt driven touchscreen driver
Date: Thu, 4 Jun 2009 11:38:07 +0100 [thread overview]
Message-ID: <20090604103807.GG6983@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <s5hiqjcqqo9.wl%tiwai@suse.de>
On Thu, Jun 04, 2009 at 11:44:22AM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > There was a very strong pushback against the idea of adding a void *
> > to the structure, which is what I'd be looking for.
> Yes, I was against the void pointer because there is no guarantee
> of the data-type correctness between the data and the user.
> The normal drvdata is fine because the creator and the user are the
> same. But, the proposal of private_driver_data (of the last one, at
> least) is no such a scenario.
Do you have a pointer to this proposal? I don't remember it and my
google-fu is weak today.
next prev parent reply other threads:[~2009-06-04 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 21:41 [PATCH] Palm interrupt driven touchscreen driver Marek Vasut
2009-06-04 1:35 ` Eric Miao
2009-06-04 7:20 ` Ian Molton
2009-06-04 8:54 ` Mark Brown
2009-06-04 9:09 ` Jaroslav Kysela
2009-06-04 9:37 ` Mark Brown
2009-06-04 9:44 ` Takashi Iwai
2009-06-04 10:38 ` Mark Brown [this message]
2009-06-05 9:16 ` Takashi Iwai
2009-06-05 9:30 ` Mark Brown
2009-06-05 10:05 ` Takashi Iwai
2009-06-05 10:20 ` Mark Brown
2009-06-05 10:38 ` Takashi Iwai
2009-06-05 10:42 ` Mark Brown
2009-06-04 9:13 ` Russell King - ARM Linux
2009-06-04 9:27 ` Mark Brown
2009-06-04 8:14 ` Russell King - ARM Linux
2009-06-04 20:05 ` Marek Vasut
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=20090604103807.GG6983@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux@arm.linux.org.uk \
--cc=marek.vasut@gmail.com \
--cc=tiwai@suse.de \
/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.