The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Arnd Bergmann <arndbergmann@googlemail.com>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: bkl: Pushdowns for sound/oss ?
Date: Fri, 21 May 2010 15:45:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1005211536330.25348@localhost.localdomain> (raw)

Hi Ralf

I was looking at doing some of that last remaining ioctl bkl-pushdowns, in 
particular in:
sound/oss/swarm_cs4297a.c
sound/oss/msnd_pinnacle.c
sound/oss/sh_dac_audio.c
sound/oss/vwsnd.c
sound/oss/dmasound/dmasound_core.c
sound/oss/dmasound/dmasound_core.c

when I noticed they were including asm files from mips. I went so far as 
to compile my own mips tool chain, but I wasn't able to compile the above.
Being oss sound, I was wondering if these are still maintained or are 
marked for removal some time in the future.

If there is merely a problem with my toolchain, then that can be fixed, 
but there is no point in wasting time with these if no-one uses them.

Thanks

John

             reply	other threads:[~2010-05-21 13:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 13:45 John Kacur [this message]
2010-05-21 14:06 ` bkl: Pushdowns for sound/oss ? Christoph Hellwig
2010-05-23  8:36   ` Geert Uytterhoeven
2010-05-21 14:40 ` Ralf Baechle
2010-05-21 14:52   ` Paul Mundt
2010-05-21 15:32   ` Clemens Ladisch
2010-05-22  7:13     ` Krzysztof Helt
2010-05-21 15:34   ` Maciej W. Rozycki
2010-05-21 15:46     ` Ralf Baechle
2010-05-22 21:26       ` Maciej W. Rozycki
2010-05-21 16:12   ` Mark Brown

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=alpine.LFD.2.00.1005211536330.25348@localhost.localdomain \
    --to=jkacur@redhat.com \
    --cc=arndbergmann@googlemail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox