From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning from Linus' tree
Date: Fri, 30 Aug 2019 10:25:53 +1000 [thread overview]
Message-ID: <20190830102553.38fd43f2@canb.auug.org.au> (raw)
In-Reply-To: <alpine.DEB.2.21.1908300028360.1938@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
Hi Thomas,
On Fri, 30 Aug 2019 00:29:21 +0200 (CEST) Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Fri, 30 Aug 2019, Stephen Rothwell wrote:
>
> Yes. We have a fix queued which should hit next tomorrow.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-30 0:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 22:23 linux-next: build warning from Linus' tree Stephen Rothwell
2019-08-29 22:29 ` Thomas Gleixner
2019-08-30 0:25 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-01 7:20 Stephen Rothwell
2021-07-08 2:25 ` Stephen Rothwell
2021-07-20 7:31 ` Stephen Rothwell
2021-08-10 9:29 ` Stephen Rothwell
2017-02-26 23:23 Stephen Rothwell
2011-06-03 1:10 Stephen Rothwell
2011-06-03 14:17 ` David Sterba
2011-06-03 1:00 Stephen Rothwell
2010-10-27 0:29 Stephen Rothwell
2010-10-27 0:58 ` Jesse Gross
2010-10-27 0:00 Stephen Rothwell
2010-09-24 4:08 Stephen Rothwell
2010-09-24 12:32 ` Frederic Weisbecker
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=20190830102553.38fd43f2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).