From: Hans-Joachim Picht <hans@linux•vnet.ibm.com>
To: Takashi Iwai <tiwai@suse•de>
Cc: linux-next@vger•kernel.org
Subject: Re: [PATCH] fix I/O memory related compile caused by wrong Kconfig dependencies
Date: Wed, 21 May 2008 23:30:56 +0200 [thread overview]
Message-ID: <20080521213056.GA22707@blc4eb509856389.ibm.com> (raw)
In-Reply-To: <s5hve17vd9y.wl%tiwai@suse.de>
On Wed, May 21, 2008 at 06:21:29PM +0200, Takashi Iwai wrote:
> At Wed, 21 May 2008 18:05:23 +0200, Hans-Joachim Picht wrote:
> >
> > On s390 linux-next fails with the following build error:
> >
> > sound/core/memory.c: In function 'copy_to_user_fromio':
> > sound/core/memory.c:47: error: implicit declaration of function 'memcpy_fromio'
> > sound/core/memory.c: In function 'copy_from_user_toio':
> > sound/core/memory.c:82: error: implicit declaration of function 'memcpy_toio'
[...]
> Thanks. I prefer "depends on" in menuconfig SOUND so that we need no
> extra if-endif block. I added the patch below to sound-2.6 tree.
> Does it work for you?
Yes, it work for me.
--Hans
prev parent reply other threads:[~2008-05-21 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 16:05 [PATCH] fix I/O memory related compile caused by wrong Kconfig dependencies Hans-Joachim Picht
2008-05-21 16:21 ` Takashi Iwai
2008-05-21 21:30 ` Hans-Joachim Picht [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=20080521213056.GA22707@blc4eb509856389.ibm.com \
--to=hans@linux$(echo .)vnet.ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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