linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/51] rtc: stop using rtc deprecated functions
Date: Wed, 21 Jun 2017 00:08:05 +0200	[thread overview]
Message-ID: <20170620220805.GA11195@amd> (raw)
In-Reply-To: <CA+M3ks68+z6nDtYM8CDpso7SxjB6Nt5E=rOc1yxx=kDz6PUeVQ@mail.gmail.com>

Hi!

> >> > This is it.
> >> > https://patchwork.kernel.org/patch/6219401/
> >>
> >> Thanks.
> >>
> >> Yes, that's argument against changing rtc _drivers_ for hardware that
> >> can not do better than 32bit. For generic code (such as 44/51 sysfs,
> >> 51/51 suspend test), the change still makes sense.
> 
> What I had in mind when writing those patches was to remove the limitations
> coming from those functions usage, even more since they been marked has
> deprecated.
> 
> I agree that will change nothing of hardware limitation but at least
> the limit will
> not come from the framework.

> > Yes, we agree on that but I won't cherry pick working patches from a 51
> > patches series.

Well, it would be actually nice for you to do the cherry
picking. That's something maintainers do, because it is hard for
contributors to guess maintainer's taste.

Anyway, it looks like someone should go through all the RTC drivers,
and document their limitations of each driver (date in future when
hardware ceases to be useful). If Benjamin has time to do that, I
guess that removes all the objections to the series.

Regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170621/9ea489d7/attachment-0001.sig>

  parent reply	other threads:[~2017-06-20 22:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20  9:35 [PATCH 00/51] rtc: stop using rtc deprecated functions Benjamin Gaignard
2017-06-20  9:35 ` [PATCH 07/51] rtc: ab8500: " Benjamin Gaignard
2017-06-20 16:06   ` Linus Walleij
2017-06-21  6:57   ` kbuild test robot
2017-06-20  9:35 ` [PATCH 12/51] rtc: coh901331: " Benjamin Gaignard
2017-06-20 16:07   ` [rtc-linux] " Linus Walleij
2017-06-20 21:21   ` Russell King - ARM Linux
2017-06-20  9:35 ` [PATCH 17/51] rtc: digicolor: " Benjamin Gaignard
2017-06-20  9:35 ` [PATCH 26/51] rtc: gemini: " Benjamin Gaignard
2017-06-20  9:35 ` [PATCH 29/51] rtc: lpc32xx: " Benjamin Gaignard
2017-06-20  9:35 ` [PATCH 34/51] rtc: pl031: " Benjamin Gaignard
2017-06-20 16:08   ` Linus Walleij
2017-06-20 21:05     ` Russell King - ARM Linux
2017-06-20  9:35 ` [PATCH 39/51] rtc: sirfsoc: " Benjamin Gaignard
2017-06-20  9:35 ` [PATCH 43/51] rtc: sun6i: " Benjamin Gaignard
2017-06-20 10:03 ` [PATCH 00/51] rtc: " Alexandre Belloni
2017-06-20 10:07   ` Alexandre Belloni
2017-06-20 12:10   ` Pavel Machek
2017-06-20 12:24     ` Alexandre Belloni
2017-06-20 13:26       ` Pavel Machek
2017-06-20 13:37         ` Steve Twiss
2017-06-20 13:44           ` Pavel Machek
2017-06-20 13:48             ` Alexandre Belloni
2017-06-20 15:07               ` Benjamin Gaignard
2017-06-20 21:15                 ` Russell King - ARM Linux
2017-06-21  9:26                   ` David Laight
2017-06-21  9:35                     ` Russell King - ARM Linux
2017-06-20 22:08                 ` Pavel Machek [this message]
2017-06-21  9:14                   ` Benjamin Gaignard
     [not found] <20170620213507.urobmtg34vzubrdq@piout.net>
2017-06-20 22:00 ` Thomas Gleixner
2017-06-20 22:38   ` Russell King - ARM Linux
2017-06-21  7:51   ` Pavel Machek
2017-06-21  8:39     ` Alexandre Belloni
2017-06-21  6:34       ` Pavel Machek
2017-06-21 12:35         ` Alexandre Belloni
2017-06-21 18:08           ` Pavel Machek
2017-06-21  9:19       ` Russell King - ARM Linux
2017-06-21  9:41         ` Alexandre Belloni

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=20170620220805.GA11195@amd \
    --to=pavel@ucw.cz \
    --cc=linux-arm-kernel@lists.infradead.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).