linux-kernel - Re: [PATCH] hpet: factor timer allocate from open

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 18 Mar 2010 12:11:51 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Magnus Lynch <maglyx@...il.com>
Cc:	Clemens Ladisch <clemens@...isch.de>,
	"Venkatesh Pallipadi (Venki)" <venkatesh.pallipadi@...el.com>,
	"Vojtech Pavlik" <vojtech@...e.cz>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Paul Gortmaker" <paul.gortmaker@...driver.com>,
	"Suresh Siddha" <suresh.b.siddha@...el.com>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hpet: factor timer allocate from open

On Sun, 07 Mar 2010 16:04:39 -0800 (PST)
Magnus Lynch <maglyx@...il.com> 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@...il.com>

(wonders what this patch does)

Please always retain and maintain the changelog with each version of a patch.

Please resend this patch with a complete changelog.  Make sure that the
changelog addresses any questions which were raised during review. 
Please ensure that all participants in that review were cc'ed.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/