From: Takashi Iwai <tiwai@suse.de>
To: Bryan Wu <cooloney@kernel.org>
Cc: perex@perex.cz, liam.girdwood@wolfsonmicro.com,
broonie@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, Cliff Cai <cliff.cai@analog.com>
Subject: Re: [PATCH 4/4] ALSA: add dummy function to support shared mmap in nommu Blackfin arch
Date: Thu, 28 Aug 2008 14:44:32 +0200 [thread overview]
Message-ID: <s5h4p559umn.wl%tiwai@suse.de> (raw)
In-Reply-To: <1219829968-6431-5-git-send-email-cooloney@kernel.org>
At Wed, 27 Aug 2008 17:39:28 +0800,
Bryan Wu wrote:
>
> From: Cliff Cai <cliff.cai@analog.com>
>
> Signed-off-by: Cliff Cai <cliff.cai@analog.com>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
> ---
> sound/core/pcm_native.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/sound/core/pcm_native.c b/sound/core/pcm_native.c
> index c49b9d9..cb202a1 100644
> --- a/sound/core/pcm_native.c
> +++ b/sound/core/pcm_native.c
> @@ -3391,6 +3391,12 @@ out:
> }
> #endif /* CONFIG_SND_SUPPORT_OLD_API */
>
> +unsigned long dummy_get_unmapped_area(struct file *file, unsigned long addr,
> + unsigned long len, unsigned long pgoff, unsigned long flags)
> +{
> + return 0;
> +}
Always zero is confirmed to work for other architectures, too?
> /*
> * Register section
> */
> @@ -3407,6 +3413,7 @@ const struct file_operations snd_pcm_f_ops[2] = {
> .compat_ioctl = snd_pcm_ioctl_compat,
> .mmap = snd_pcm_mmap,
> .fasync = snd_pcm_fasync,
> + .get_unmapped_area = dummy_get_unmapped_area,
> },
> {
> .owner = THIS_MODULE,
> @@ -3419,5 +3426,6 @@ const struct file_operations snd_pcm_f_ops[2] = {
> .compat_ioctl = snd_pcm_ioctl_compat,
> .mmap = snd_pcm_mmap,
> .fasync = snd_pcm_fasync,
> + .get_unmapped_area = dummy_get_unmapped_area,
> }
> };
I don't think adding this dummy get_unmapped_area unconditionally for
every driver is good. This overrides the default
mm->get_unmaped_area.
Takashi
next prev parent reply other threads:[~2008-08-28 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 9:39 [PATCH 0/4] Blackfin supports for ALSA/ASOC Bryan Wu
2008-08-27 9:39 ` [PATCH 1/4] ASOC: Blackfin driver for ALSA SoC framework Bryan Wu
2008-08-27 13:48 ` Mark Brown
2008-09-03 4:09 ` Cai, Cliff
2008-09-03 10:38 ` Mark Brown
2008-09-04 3:54 ` [alsa-devel] " Cliff Cai
2008-08-27 9:39 ` [PATCH 2/4] ASOC codec: add support for SSM2602 audio codec in " Bryan Wu
2008-08-27 10:54 ` [alsa-devel] " Mark Brown
2008-08-28 5:55 ` Bryan Wu
2008-08-28 10:06 ` Mark Brown
2008-08-28 11:44 ` Jean Delvare
2008-08-27 9:39 ` [PATCH 3/4] ASOC: WM8731 codec: add SPI support as well as I2C Bryan Wu
2008-08-27 11:01 ` [alsa-devel] " Mark Brown
2008-08-28 3:46 ` Bryan Wu
2008-08-28 10:14 ` Mark Brown
2008-08-28 12:47 ` Takashi Iwai
2008-08-28 13:01 ` Mark Brown
2008-09-01 13:52 ` Alan Horstmann
2008-09-01 14:00 ` Liam Girdwood
2008-09-01 14:02 ` Mark Brown
2008-08-27 9:39 ` [PATCH 4/4] ALSA: add dummy function to support shared mmap in nommu Blackfin arch Bryan Wu
2008-08-28 12:44 ` Takashi Iwai [this message]
2008-09-02 3:16 ` Cai, Cliff
2008-09-02 9:41 ` Takashi Iwai
2008-09-02 9:59 ` Bryan Wu
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=s5h4p559umn.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cliff.cai@analog.com \
--cc=cooloney@kernel.org \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®