linux-kernel - Re: [PATCH 2/4] hrtimer: export __hrtimer_start_range

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]

Message-ID: <alpine.DEB.2.02.1403191053220.18573@ionos.tec.linutronix.de>
Date:	Wed, 19 Mar 2014 10:53:34 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	"Yan, Zheng" <zheng.z.yan@...el.com>, linux-kernel@...r.kernel.org,
	mingo@...nel.org, acme@...radead.org, eranian@...gle.com,
	andi@...stfloor.org
Subject: Re: [PATCH 2/4] hrtimer: export __hrtimer_start_range_ns

On Wed, 19 Mar 2014, Peter Zijlstra wrote:

> On Tue, Mar 18, 2014 at 04:56:42PM +0800, Yan, Zheng wrote:
> > export __hrtimer_start_range_ns() to allow building perf Intel uncore
> > driver as module
> 
> Bah; you didn't cc the hrtimer maintainer.
> 
> Thomas, ack on this?

Yup.
 
> > Signed-off-by: Yan, Zheng <zheng.z.yan@...el.com>
> > ---
> >  kernel/hrtimer.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
> > index 0909436..650bf38 100644
> > --- a/kernel/hrtimer.c
> > +++ b/kernel/hrtimer.c
> > @@ -1030,6 +1030,7 @@ int __hrtimer_start_range_ns(struct hrtimer *timer, ktime_t tim,
> >  
> >  	return ret;
> >  }
> > +EXPORT_SYMBOL_GPL(__hrtimer_start_range_ns);
> >  
> >  /**
> >   * hrtimer_start_range_ns - (re)start an hrtimer on the current CPU
> > -- 
> > 1.8.5.3
> > 
> 
--
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/