From: Alessandro Zummo <a.zummo@towertech.it>
To: Alexander Holler <holler@ahsoftware.de>
Cc: John Stultz <john.stultz@linaro.org>,
John Whitmore <arigead@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: rtc/hctosys.c Problem during kernel boot
Date: Thu, 12 Jun 2014 15:15:05 +0200 [thread overview]
Message-ID: <20140612151505.03defe29@linux.lan.towertech.it> (raw)
In-Reply-To: <539996AA.6020205@ahsoftware.de>
On Thu, 12 Jun 2014 14:01:46 +0200
Alexander Holler <holler@ahsoftware.de> wrote:
> Unfortunately my expieriences with Linux kernel maintainers became even
> worse and I'm not very eager to post patches. But if someone wants these
> patches based on 3.15, feel free to notice me.
>
> To get rid of hctosys, I have 3 patches, and 2 more to implement
> rtc_read_timeval() for higher resolution clocks.
Yes, I know the experience might be a painful one.
Please send the patches and let's see if they fix the issue for John too.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2014-06-12 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 23:01 rtc/hctosys.c Problem during kernel boot John Whitmore
2014-06-11 23:53 ` John Stultz
2014-06-12 1:06 ` John Whitmore
2014-06-12 12:01 ` Alexander Holler
2014-06-12 13:15 ` Alessandro Zummo [this message]
2014-06-13 4:13 ` [PATCH 1/3] RFC: timekeeping: introduce flag systime_was_set Alexander Holler
2014-06-13 4:13 ` [PATCH 2/3] RFC: timekeeping: rtc: Introduce new kernel parameter hctosys Alexander Holler
2014-06-13 4:13 ` [PATCH 3/3] RFC: timekeeping: rtc: remove CONFIG_RTC_HCTOSYS and RTC_HCTOSYS_DEVICE Alexander Holler
2014-06-21 13:08 ` rtc/hctosys.c Problem during kernel boot Alexander Holler
2014-06-21 13:21 ` Alessandro Zummo
2014-06-23 21:36 ` John Stultz
2014-06-24 5:37 ` Alexander Holler
2014-06-27 8:47 ` 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=20140612151505.03defe29@linux.lan.towertech.it \
--to=a.zummo@towertech.it \
--cc=arigead@gmail.com \
--cc=holler@ahsoftware.de \
--cc=john.stultz@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).