All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] re-export cancel_rearming_delayed_workqueue
Date: Sun, 10 Apr 2005 16:11:46 -0500	[thread overview]
Message-ID: <1113167506.6737.21.camel@mulgrave> (raw)
In-Reply-To: <1113162531.15213.0.camel@laptopd505.fenrus.org>

On Sun, 2005-04-10 at 21:48 +0200, Arjan van de Ven wrote:
> I have absolutely no problem with such an export / unstatic if there are
> users... could you just send them in one go ?

Actually, no ... this is a nasty cross tree dependency.  The piece of
code is queued in the parisc tree, but Matthew can't really send it to
Linus until the interface it uses is in the tree.  It's someone else's
code, I just fixed its problems.

James





      reply	other threads:[~2005-04-10 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 19:07 [PATCH] re-export cancel_rearming_delayed_workqueue James Bottomley
2005-04-10 19:48 ` Arjan van de Ven
2005-04-10 21:11   ` James Bottomley [this message]

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=1113167506.6737.21.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@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 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.