public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Dmitry Torokhov <dtor-oss@comcast.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Takashi Iwai <tiwai@suse.de>,
	Linux kernel <linux-kernel@vger.kernel.org>,
	Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [patch] pcspkr: fix dependancies
Date: Sun, 27 Apr 2008 03:39:37 +0400	[thread overview]
Message-ID: <4813BD39.1080105@aknet.ru> (raw)
In-Reply-To: <200804261918.14711.dtor-oss@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

Hello.

Dmitry Torokhov wrote:
> No, not another config option please. Either make pcspkr platform
> device be created unconditionally
I also think this would be the best
fix. But this will return us to the
state of 2.6.24. Presumably the dependancy
was added for the reason, even if I
fail to see one.
But in any case, the patch is attached.

> or if either pcspkr or snd-pcsp
> is selected.
I don't think it is correct, but if
people think it is, then this can be
done.


---
Compile pcspkr platform device unconditionally.
That allows snd-pcsp to work.

Signed-off-by: Stas Sergeev <stsp@aknet.ru>

[-- Attachment #2: pcsp_dep1.diff --]
[-- Type: text/x-patch, Size: 387 bytes --]

--- a/arch/x86/kernel/Makefile	2008-04-26 13:40:06.000000000 +0400
+++ b/arch/x86/kernel/Makefile	2008-04-26 18:22:49.000000000 +0400
@@ -83,9 +83,7 @@
 obj-$(CONFIG_VMI)		+= vmi_32.o vmiclock_32.o
 obj-$(CONFIG_PARAVIRT)		+= paravirt.o paravirt_patch_$(BITS).o
 
-ifdef CONFIG_INPUT_PCSPKR
 obj-y				+= pcspeaker.o
-endif
 
 obj-$(CONFIG_SCx200)		+= scx200.o
 scx200-y			+= scx200_32.o

  reply	other threads:[~2008-04-26 23:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 15:16 [patch] pcspkr: fix dependancies Stas Sergeev
2008-04-26 23:18 ` Dmitry Torokhov
2008-04-26 23:39   ` Stas Sergeev [this message]
2008-04-27  4:23     ` Dmitry Torokhov
2008-04-28 19:34       ` Stas Sergeev
2008-04-28 19:58         ` Dmitry Torokhov
2008-04-28 20:12           ` Sam Ravnborg
2008-04-28 20:19             ` Dmitry Torokhov
2008-04-29 19:56             ` Stas Sergeev
2008-04-30  7:31               ` Michael Opdenacker
2008-04-30 11:23                 ` Stas Sergeev
2008-05-01  7:08                 ` Stas Sergeev
  -- strict thread matches above, loose matches on Subject: below --
2008-05-04  4:22 [patch][resend] " Stas Sergeev
2008-05-05  3:57 ` Dmitry Torokhov
2008-05-05  4:26   ` Stas Sergeev
2008-05-05  4:35     ` Dmitry Torokhov
2008-05-05  5:02       ` [patch][resend2] " Stas Sergeev
2008-05-05 11:02         ` Takashi Iwai
2008-05-08 17:50           ` [patch] " Stas Sergeev
2008-05-08 13:58             ` Takashi Iwai

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=4813BD39.1080105@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=akpm@linux-foundation.org \
    --cc=dtor-oss@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=vojtech@suse.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