mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Dmitry Torokhov <dtor-oss@comcast.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Takashi Iwai <tiwai@suse.de>,
	Linux kernel <linux-kernel@vger.kernel.org>,
	Vojtech Pavlik <vojtech@suse.cz>,
	Michael Opdenacker <michael@free-electrons.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch] pcspkr: fix dependancies
Date: Sun, 27 Apr 2008 00:23:31 -0400	[thread overview]
Message-ID: <20080427042331.GB29127@anvil.corenet.prv> (raw)
In-Reply-To: <4813BD39.1080105@aknet.ru>

On Sun, Apr 27, 2008 at 03:39:37AM +0400, Stas Sergeev wrote:
> 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.
> 

It looks like the change was introduced by commit

67926892ef7a7fbc76de607120d44416019fdf07

I think that we should register devices even if there is no driver in
the kernel for it because driver may be compiled at later time or be out
of tree. Adding patch author and other people that signed off the patch
to CC...

> 
> ---
> Compile pcspkr platform device unconditionally.
> That allows snd-pcsp to work.
> 
> Signed-off-by: Stas Sergeev <stsp@aknet.ru>

> --- 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


-- 
Dmitry

  reply	other threads:[~2008-04-27  4:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 15:16 Stas Sergeev
2008-04-26 23:18 ` Dmitry Torokhov
2008-04-26 23:39   ` Stas Sergeev
2008-04-27  4:23     ` Dmitry Torokhov [this message]
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
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=20080427042331.GB29127@anvil.corenet.prv \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dtor-oss@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@free-electrons.com \
    --cc=mingo@elte.hu \
    --cc=stsp@aknet.ru \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®