mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH 2.6.19-rc1-mm1] Export jiffies_to_timespec()
Date: Sat, 28 Oct 2006 17:50:02 +0100	[thread overview]
Message-ID: <20061028165002.GB22673@infradead.org> (raw)
In-Reply-To: <20061011111739.09c25a8e.akpm@osdl.org>

On Wed, Oct 11, 2006 at 11:17:39AM -0700, Andrew Morton wrote:
> On Wed, 11 Oct 2006 17:16:28 +0100
> Christoph Hellwig <hch@infradead.org> wrote:
> 
> > On Tue, Oct 10, 2006 at 05:36:54PM -0700, Jeremy Fitzhardinge wrote:
> > > Export jiffies_to_timespec; previously modules used the inlined header 
> > > version.
> > 
> > NACK, drivers shouldn know about these timekeeping details and no
> > in-tree driver uses it (fortunately)
> 
> Disagree.
> 
> a) `jiffies' and `timepsec' are hardly "details".  They are basic
>    kernel-wide concepts.  timespecs are even known to userspace.  Exporting
>    a helper function which converts from one to the other is perfectly
>    reasonable.

That non one in tree ever uses it is a very good reason no to export it
either.  While there are still far too many direct jiffy users there
is no one directly convertin it to a timespec for good reason.

> 
> b) jiffies_to_timespec() was previously available to modules.  We
>    changed that without notice and we changed it *by accident*.  There was
>    no intention to withdraw jiffies_to_timespec() from the
>    available-to-modules API.

By that rationale everything errornously implemented as a macro or inline
at some point will need to be exported.  Except for you we still maintain
that we don't want to keep unused exports.  Arjan even put a formal mechanism
in to warn about them and has gotten a global buy-in to kill them.  This
will fall under this ASAP and only give people a short period to keep using
it.  Not a very useful message.

(especially when the only user is closed source crap where people should
help the proper reverse-engineered driver instead)


  reply	other threads:[~2006-10-28 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11  0:36 Jeremy Fitzhardinge
2006-10-11  7:02 ` Arjan van de Ven
2006-10-11  7:07   ` Jeremy Fitzhardinge
2006-10-11 16:16 ` Christoph Hellwig
2006-10-11 18:17   ` Andrew Morton
2006-10-28 16:50     ` Christoph Hellwig [this message]
2006-10-11 19:48   ` Jeremy Fitzhardinge

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=20061028165002.GB22673@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=jeremy@goop.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®