public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: WARN_ON(): proc_dir_entry 'rtc' already registered
Date: Sat, 8 Mar 2008 14:50:48 -0800	[thread overview]
Message-ID: <200803081450.48579.david-b@pacbell.net> (raw)
In-Reply-To: <20080219101246.GB2202@elf.ucw.cz>

On Tuesday 19 February 2008, Pavel Machek wrote:
> On Mon 2008-02-18 03:08:16, David Brownell wrote:
> > On Monday 18 February 2008, Pavel Machek wrote:
> > > > How to fix ... how about:  instead of just warning folk
> > > > off such legacy RTC drivers [1] we just wrap them with
> > > > an "if RTC_LIB != n" so this mistake won't be possible.
> > > 
> > > Yes, disabling bad configs in Kconfig seems like way to go.
> > 
> > Problem is ... that also disables valid configs that
> > get assembled by picking the right module(s) for the
> > target system.
> 
> Is there any reason to use the old rtc subsystem?
> 
> At least OLD_RTC=y NEW_RTC=y should be disabled... even if OLD_RTC=m
> NEW_RTC=m makes some sense.

The patch I sent earlier today makes the two mutually exclusive.

Note by the way that there is no OLD_RTC analogue ... just a bunch
of individual drivers.


      reply	other threads:[~2008-03-08 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 13:26 WARN_ON(): proc_dir_entry 'rtc' already registered Pavel Machek
2008-02-12 18:29 ` David Brownell
2008-02-18 10:54   ` Pavel Machek
2008-02-18 11:08     ` David Brownell
2008-02-19 10:12       ` Pavel Machek
2008-03-08 22:50         ` David Brownell [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=200803081450.48579.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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