From: Alexander Holler <holler@ahsoftware.de>
To: Roman Fietze <roman.fietze@telemotive.de>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [PATCH 2/2] Allow to override the hctosys RTC using a kernel parameter
Date: Mon, 07 Jul 2014 15:01:53 +0200 [thread overview]
Message-ID: <53BA9A41.4050001@ahsoftware.de> (raw)
In-Reply-To: <2398890.hEQ05gdLB8@rfietze>
Am 07.07.2014 13:50, schrieb Roman Fietze:
> Hello list members,
>
> And here the second part.
>
>
> From e523006a34db26c274d3b71de5b914f476fb029e Mon Sep 17 00:00:00 2001
> From: Roman Fietze <roman.fietze@telemotive.de>
> Date: Fri, 4 Jul 2014 10:05:08 +0200
> Subject: [PATCH 2/2] rtc: add kernel parameter hctosys, use it instead of
> CONFIG_RTC_HCTOSYS_DEVICE
>
> This change allows to overwrite the default of the hctosys RTC
> specified in the kernnel configuration by using a kernel parameter in
> the form of
>
> hctosys=rtc<n>
Sorry for the confusion with my replies to the other patch. The
Thunderbird on the used box got confused or confused me ("reply to list"
just replied to the rtc-list and "reply to all" didn't add the the
sender (Roman Fietze) to recipients. :/
Anyway, I think the whole rtcN mechanism is broken as you never can be
sure which driver/RTC gets which N without testing every built kernel.
I've fixed that with the already mentioned patches here:
https://lkml.org/lkml/2014/6/13/6
Besides that, I wish you luck with your patches. ;)
next prev parent reply other threads:[~2014-07-07 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 11:30 [PATCH 1/2] Allow to override the hctosys RTC using a kernel parameter Roman Fietze
2014-07-07 11:50 ` [PATCH 2/2] " Roman Fietze
2014-07-07 13:01 ` Alexander Holler [this message]
2014-07-15 23:15 ` [rtc-linux] " Andrew Morton
2014-07-07 12:20 ` [rtc-linux] [PATCH 1/2] " Alexander Holler
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=53BA9A41.4050001@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=roman.fietze@telemotive.de \
--cc=rtc-linux@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.