From: Greg KH <gregkh@suse.de>
To: Stas Sergeev <stsp@aknet.ru>
Cc: tiwai@suse.de, Linux kernel <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: patch driver-core-warn-about-duplicate-driver-names-on-the-same-bus.patch added to gregkh-2.6 tree
Date: Mon, 28 Apr 2008 21:58:49 -0700 [thread overview]
Message-ID: <20080429045849.GA6348@suse.de> (raw)
In-Reply-To: <4816A888.9000802@aknet.ru>
On Tue, Apr 29, 2008 at 08:48:08AM +0400, Stas Sergeev wrote:
> Hello.
>
> gregkh@suse.de wrote:
> > This is a note to let you know that I've just added the patch titled
> > Subject: driver core: warn about duplicate driver names on the same bus
> > to my gregkh-2.6 tree. Its filename is
> Thanks.
>
> Takashi, do you think this fixes the
> pcspkr/snd-pcsp conflict sufficienly
> well? I think the Kconfig protection
> is no longer needed. For the better
> convinience the modprobe rule can be
> created that will remove one driver
> before inserting another. But this is
> optional.
No, don't rely on the driver core warning and catching code errors like
this, that's not a good idea at all. I like the warning and your patch,
but don't assume it's always going to be there.
thanks,
greg k-h
next prev parent reply other threads:[~2008-04-29 5:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12094266793898@kroah.org>
2008-04-29 4:48 ` patch driver-core-warn-about-duplicate-driver-names-on-the-same-bus.patch added to gregkh-2.6 tree Stas Sergeev
2008-04-29 4:58 ` Greg KH [this message]
2008-04-29 10:41 ` Takashi Iwai
2008-04-29 15:14 ` Greg KH
2008-04-29 16:41 ` Takashi Iwai
2008-04-29 16:56 ` Greg KH
2008-04-29 19:28 ` Stas Sergeev
2008-04-30 6:34 ` Takashi Iwai
2008-04-30 17:45 ` Stas Sergeev
2008-05-02 14:07 ` Takashi Iwai
2008-05-02 15:38 ` Stas Sergeev
2008-05-02 16:00 ` Takashi Iwai
2008-05-02 16:22 ` Stas Sergeev
2008-05-02 16:35 ` 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=20080429045849.GA6348@suse.de \
--to=gregkh@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
--cc=tiwai@suse.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