From: Thomas Gleixner <tglx@linutronix.de>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Wireless <linux-wireless@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christian Lamparter <chunkeey@gmail.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: linux-next: build failure after merge of the tip tree
Date: Tue, 25 Jun 2019 08:26:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1906250825050.32342@nanos.tec.linutronix.de> (raw)
In-Reply-To: <8736jyfaje.fsf@codeaurora.org>
On Tue, 25 Jun 2019, Kalle Valo wrote:
> Stephen Rothwell <sfr@canb.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
next prev parent reply other threads:[~2019-06-25 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 6:04 linux-next: build failure after merge of the tip tree Stephen Rothwell
2019-06-25 6:23 ` Kalle Valo
2019-06-25 6:26 ` Thomas Gleixner [this message]
2019-06-25 6:36 ` Stephen Rothwell
2019-06-25 6:51 ` Kalle Valo
2019-06-25 6:56 ` Thomas Gleixner
2019-06-25 7:47 ` Kalle Valo
2019-07-09 0:09 ` Stephen Rothwell
2019-07-09 3:46 ` Stephen Rothwell
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=alpine.DEB.2.21.1906250825050.32342@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=Jason@zx2c4.com \
--cc=chunkeey@gmail.com \
--cc=hpa@zytor.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).