linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] rtc: Allow rtc drivers to specify the tv_nsec value for ntp
Date: Mon, 27 Nov 2017 19:44:11 +0100	[thread overview]
Message-ID: <20171127184411.GA19577@piout.net> (raw)
In-Reply-To: <20171127175254.GL31757@n2100.armlinux.org.uk>

On 27/11/2017 at 17:52:54 +0000, Russell King - ARM Linux wrote:
> I'm actually rather disappointed that Alexandre Belloni has only now
> brought up his dis-satisfaction with the approach after all the effort
> that Jason and myself have put in to it.  It's not like Alexandre was
> not copied on the patches and discussion.
> 
> If Alexandre could not be bothered to bring up his concerns while the
> discussion was on-going in September, and didn't bother raising them
> in October, I'd say that Alexandre's opinion at this point doesn't
> count for much - if it wasn't important to state at the time or for
> a couple of months after, why does it become important to state after
> the thing has been merged.
> 
> Maybe the idea here is basically to waste people's time letting them
> develop a patch for an approach, and then object at the last minute
> to that approach.  Hardly seems fair or even reasonable.
> 

How unfair that is! Really, you are not in a position to make that kind
of comment because you are not even replying to patches in your own
subsystem. But maybe my time doesn't count as much as yours.

I was going to go for a middle ground but now, I'm really more inclined
to just revert the whole stuff.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-27 18:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 17:54 [PATCH] rtc: Allow rtc drivers to specify the tv_nsec value for ntp Jason Gunthorpe
2017-11-23  9:54 ` Alexandre Belloni
2017-11-23 11:23   ` Russell King - ARM Linux
2017-11-23 12:04     ` Alexandre Belloni
2017-11-23 12:53       ` Russell King - ARM Linux
2017-11-24  0:13         ` J William Piggott
2017-11-27 20:18         ` Alexandre Belloni
2017-11-27 20:29           ` Jason Gunthorpe
2017-11-28 10:03           ` Russell King - ARM Linux
2017-11-23 15:04   ` Jason Gunthorpe
2017-11-23 15:36     ` Alexandre Belloni
2017-11-23 16:10       ` Russell King - ARM Linux
2017-11-23 16:25         ` Russell King - ARM Linux
2017-11-27 18:48         ` Alexandre Belloni
2017-11-23 16:33       ` Jason Gunthorpe
2017-11-27 15:43     ` Russell King - ARM Linux
2017-11-27 17:43       ` Russell King - ARM Linux
2017-11-27 18:59         ` Jason Gunthorpe
2017-11-27 17:35   ` John Stultz
2017-11-27 17:52     ` Russell King - ARM Linux
2017-11-27 18:44       ` Alexandre Belloni [this message]
2017-11-27 18:53         ` Russell King - ARM Linux
2017-11-27 19:18           ` Russell King - ARM Linux
2017-11-27 19:31           ` Alexandre Belloni
2017-11-28 10:20             ` Russell King - ARM Linux
2017-11-30 19:39               ` Alexandre Belloni
2017-11-30 19:39               ` Alexandre Belloni
2017-11-30 19:43                 ` 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=20171127184411.GA19577@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --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).