All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Magnus Lynch <maglyx@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: "Venkatesh Pallipadi (Venki)" <venkatesh.pallipadi@intel.com>,
	Vojtech Pavlik <vojtech@suse.cz>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hpet: factor timer allocate from open
Date: Tue, 16 Mar 2010 17:01:23 +0100	[thread overview]
Message-ID: <4B9FAB53.7000709@ladisch.de> (raw)
In-Reply-To: <4b943f17.4902be0a.5bd5.0917@mx.google.com>

Magnus Lynch wrote:
> Clemens Ladisch wrote:
>>> If so I can change that. I did add the explicit form of allocating
>>> timers to accomodate such a case hypothetically (open, allocate timer,
>>> get info).
>>
>> This wouldn't be backwards compatible.
> 
> OK, here's a version that retains HPET_INFO semantics.
> 
> Signed-off-by: Magnus Lynch <maglyx@gmail.com>

Acked-by: Clemens Ladisch <clemens@ladisch.de>

  reply	other threads:[~2010-03-16 16:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01  5:30 [PATCH] hpet: factor timer allocate from open Magnus Lynch
2010-03-01  9:59 ` Clemens Ladisch
2010-03-01 20:24   ` Magnus Lynch
2010-03-01 20:59     ` john stultz
2010-03-03  9:07       ` Magnus Lynch
2010-03-03 16:26         ` john stultz
2010-03-10  2:47           ` Magnus Lynch
2010-03-04  2:59   ` Magnus Lynch
2010-03-04  8:43     ` Clemens Ladisch
2010-03-08  0:04       ` Magnus Lynch
2010-03-16 16:01         ` Clemens Ladisch [this message]
2010-03-18 19:11         ` Andrew Morton
2010-03-19  4:06           ` Magnus Lynch
2010-03-22 22:21             ` Andrew Morton
2010-03-23  2:02               ` Magnus Lynch

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=4B9FAB53.7000709@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maglyx@gmail.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=vojtech@suse.cz \
    /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.