From: David Miller <davem@davemloft.net>
To: david-b@pacbell.net
Cc: James.Bottomley@hansenpartnership.com,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
alessandro.zummo@towertech.it
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Mon, 08 Sep 2008 19:52:35 -0700 (PDT) [thread overview]
Message-ID: <20080908.195235.200905674.davem@davemloft.net> (raw)
In-Reply-To: <200809081755.26148.david-b@pacbell.net>
From: David Brownell <david-b@pacbell.net>
Date: Mon, 8 Sep 2008 17:55:25 -0700
> On Monday 08 September 2008, David Miller wrote:
> > From: David Brownell <david-b@pacbell.net>
> > Date: Mon, 8 Sep 2008 16:29:20 -0700
> >
> > > That said, there's a bit of unresolved stuff around NTP hooks
> > > in the kernel. Some patches are pending to let thtem work with
> > > the RTC framework -- where writing an RTC may need to sleep,
> > > for example because the RTC is on an I2C or SPI bus. And
> > > then there's the discussion of whether that shouldn't all be
> > > handled by NTPD anyway, no special kernel support desired.
> > > Alessandro has opinions there. ;)
> >
> > My update_persistent_clock() on sparc64 is:
> >
> > int update_persistent_clock(struct timespec now)
> > {
> > struct rtc_device *rtc = rtc_class_open("rtc0");
>
> I'd be tempted to cache that ... notice how you never
> close it, too. That will goof lots of refcounts...
Well if I cache it then we'll hold it forever and that's not
so nice right?
I'm going to put the missing rtc_close() in there for now to
fix the leak.
I'm happy to cache this if you think it's warranted, but then
this is like saying that the refcount doesn't matter :-)
> =============== CUT ON THE DOTTED LINE ==================
> Subject: ntp: let update_persistent_clock() sleep
> From: "Maciej W. Rozycki" <macro@linux-mips.org>
I see, as Paul mentioned this is needed for stuff like RTCs
behind I2C.
This change isn't in Linus's tree yet.
next prev parent reply other threads:[~2008-09-09 2:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 15:53 [PATCH] fix RTC_CLASS regression with PARISC James Bottomley
2008-09-08 18:19 ` David Brownell
2008-09-08 18:39 ` James Bottomley
2008-09-08 19:13 ` David Brownell
2008-09-08 20:28 ` James Bottomley
2008-09-08 21:29 ` David Brownell
2008-09-08 21:29 ` David Brownell
2008-09-08 21:35 ` David Miller
2008-09-08 23:00 ` James Bottomley
2008-09-08 23:04 ` David Miller
2008-09-08 23:23 ` James Bottomley
2008-09-08 23:32 ` David Brownell
2008-09-08 23:32 ` David Brownell
2008-09-08 23:43 ` David Miller
2008-09-08 23:29 ` David Brownell
2008-09-08 23:44 ` David Miller
2008-09-09 0:55 ` David Brownell
2008-09-09 2:52 ` David Miller [this message]
2008-09-09 3:17 ` David Brownell
2008-09-09 3:17 ` David Brownell
2008-09-09 3:51 ` David Miller
2008-09-09 3:51 ` David Miller
2008-09-09 4:14 ` David Brownell
2008-09-09 4:14 ` David Brownell
2008-09-10 21:04 ` Andrew Morton
2008-09-10 21:09 ` Randy.Dunlap
2008-09-10 21:19 ` David Brownell
2008-09-10 21:19 ` David Brownell
2008-09-10 21:20 ` David Miller
2008-09-10 21:20 ` David Miller
2008-09-10 21:36 ` David Brownell
2008-09-10 21:36 ` David Brownell
2008-09-10 21:40 ` David Miller
2008-09-09 1:22 ` Paul Mackerras
2008-09-08 21:37 ` James Bottomley
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=20080908.195235.200905674.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=alessandro.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.