From: Andreas Schwab <schwab@redhat.com>
To: Andy Clark <andy.apcs@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [x86] x86 targets without CMOS still build rtc.c despite CONFIG_RTC unset
Date: Mon, 20 Sep 2010 13:58:45 +0200 [thread overview]
Message-ID: <m3fwx48w3u.fsf@hase.home> (raw)
In-Reply-To: <AANLkTimigBxKWaJ6LNxu6a0uXo8+LOfzcoE8bVsXZ1bW@mail.gmail.com> (Andy Clark's message of "Mon, 20 Sep 2010 12:49:38 +0100")
Andy Clark <andy.apcs@googlemail.com> writes:
> I haven't taken the time to fully understand the build mechanism, but
> comparing the x86 with other targets, the x86 target doesn't appear to
> support CONFIG_RTC. Leaving this unset doesn't prevent
> arch/x86/kernel/rtc.c being built into the kernel.
CONFIG_RTC is unrelated to arch/x86/kernel/rtc.c. It controls
drivers/char/rtc.c.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
prev parent reply other threads:[~2010-09-20 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 11:49 Andy Clark
2010-09-20 11:58 ` Andreas Schwab [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=m3fwx48w3u.fsf@hase.home \
--to=schwab@redhat.com \
--cc=andy.apcs@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
/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®