From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, 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 09:51:01 +0300 [thread overview]
Message-ID: <87y31qdup6.fsf@codeaurora.org> (raw)
In-Reply-To: <20190625163608.1aa15ad3@canb.auug.org.au> (Stephen Rothwell's message of "Tue, 25 Jun 2019 16:36:08 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> Thanks for the report. Any suggestions how to handle this? Or do we let
>> Linus take care of this?
>
> Just let Linus take care of it ... mention it in the pull request ...
Thanks, I'll do that.
> I guess DaveM needs to know, right?
Yeah, this commit goes from wireless-drivers-next to net-next and from
there to Linus. I'll inform Dave in my pull request.
--
Kalle Valo
next prev parent reply other threads:[~2019-06-25 6:51 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
2019-06-25 6:36 ` Stephen Rothwell
2019-06-25 6:51 ` Kalle Valo [this message]
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=87y31qdup6.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Jason@zx2c4.com \
--cc=chunkeey@gmail.com \
--cc=hpa@zytor.com \
--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 \
--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).