[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1906250825050.32342@nanos.tec.linutronix.de>
Date: Tue, 25 Jun 2019 08:26:40 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Kalle Valo <kvalo@...eaurora.org>
cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Wireless <linux-wireless@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Christian Lamparter <chunkeey@...il.com>,
"Jason A. Donenfeld" <Jason@...c4.com>
Subject: Re: linux-next: build failure after merge of the tip tree
On Tue, 25 Jun 2019, Kalle Valo wrote:
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
> > ---
> > drivers/net/wireless/intersil/p54/txrx.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/intersil/p54/txrx.c b/drivers/net/wireless/intersil/p54/txrx.c
> > index be6968454282..873fea59894f 100644
> > --- a/drivers/net/wireless/intersil/p54/txrx.c
> > +++ b/drivers/net/wireless/intersil/p54/txrx.c
> > @@ -383,7 +383,7 @@ static int p54_rx_data(struct p54_common *priv, struct sk_buff *skb)
> >
> > fc = ((struct ieee80211_hdr *)skb->data)->frame_control;
> > if (ieee80211_is_probe_resp(fc) || ieee80211_is_beacon(fc))
> > - rx_status->boottime_ns = ktime_get_boot_ns();
> > + rx_status->boottime_ns = ktime_get_boottime_ns();
>
> Thanks for the report. Any suggestions how to handle this? Or do we let
> Linus take care of this?
As the core changes which cause this are in tip timers/core, I can just
pick that up and be done with it. Ok?
Thanks,
tglx
Powered by blists - more mailing lists