From: Christoph Hellwig <hch@infradead.org>
To: Karel Zak <kzak@redhat.com>
Cc: kerolasa@gmail.com, Bernhard Voelker <mail@bernhard-voelker.de>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH] hwclock: stop supporting alpha cpu architecture
Date: Mon, 30 Jul 2018 00:29:06 -0700 [thread overview]
Message-ID: <20180730072905.GA32653@infradead.org> (raw)
In-Reply-To: <20180724123052.szmsn3yguneebree@ws.net.home>
On Tue, Jul 24, 2018 at 02:30:52PM +0200, Karel Zak wrote:
> > >> -#if defined(__alpha__) || defined(__sparc__)
> > >> - /*
> > >> - * Not all alpha kernels reject RTC_UIE_ON, but probably
> > >> - * they should.
> > >> - */
> > >> - rc = -1;
> > >> - errno = EINVAL;
> > >> -#else
> > >> rc = ioctl(rtc_fd, RTC_UIE_ON, 0);
> > >> -#endif
> > >
> > > Are you sure you want to change the code path for SPARC?
> >
> > Hi Berny,
> >
> > After reading linux kernel code, and trying to find references where sparc
> > condition might be originating I could not find good reason why sparc should
> > hard code RTC_UIE_ON not to be supported. There is message from 2005 about
> > chrony having issue with sparc RTC_UIE_ON, but later in that thread Dave
> > Miller tells there is no problem with rtc and sparc. I am fairly confident
> > ioctl(rtc_fd, RTC_UIE_ON, 0) will either do the right thing or return -1.
> >
> > Reference: https://lists.debian.org/debian-sparc/2005/04/msg00115.html
>
> Maybe the best would be to postpone this to v2.34 and in v2.33 just
> inform about this plan. Frankly, I'm not sure where and what is
> supported for alpha...
Note that for modern kernel RTC support uses a lot more common code
so some of the old quirks should be dead. It might be a better idea
to approach this as dropping support for long obsolete kernels on
not common architectures, although that might require a bit more
research and testing.
next prev parent reply other threads:[~2018-07-30 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 21:13 [PATCH] hwclock: stop supporting alpha cpu architecture Sami Kerola
2018-06-27 5:58 ` Bernhard Voelker
2018-06-27 21:24 ` Sami Kerola
2018-07-24 12:30 ` Karel Zak
2018-07-30 7:29 ` Christoph Hellwig [this message]
2018-08-03 11:05 ` Karel Zak
2018-08-03 11:18 ` Karel Zak
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=20180730072905.GA32653@infradead.org \
--to=hch@infradead.org \
--cc=kerolasa@gmail.com \
--cc=kzak@redhat.com \
--cc=mail@bernhard-voelker.de \
--cc=util-linux@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