All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux-Next Mailing List" <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: linux-next: build warning after merge of the mac80211-next tree
Date: Wed, 09 May 2018 09:44:12 +0200	[thread overview]
Message-ID: <1525851852.6910.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20180509145624.643d2e56@canb.auug.org.au>

Thanks Stephen,

The 0-day bot also gave me this heads-up, there are a few more places
like it too. I'd asked Toke to fix the ones in the stack, but we both
missed the ones in the drivers. I'll get a fix in for that one way or
the other.

johannes

  reply	other threads:[~2018-05-09  7:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09  4:56 linux-next: build warning after merge of the mac80211-next tree Stephen Rothwell
2018-05-09  7:44 ` Johannes Berg [this message]
2018-05-11 12:20 ` Kalle Valo
2018-05-12  3:55   ` Stephen Rothwell
2018-05-12  3:55     ` Stephen Rothwell
2018-05-23 21:55   ` Arnd Bergmann
2018-05-23 21:55     ` Arnd Bergmann
2018-05-24  4:11     ` Kalle Valo
2018-05-24  8:51       ` Arnd Bergmann
2018-05-24  8:51         ` Arnd Bergmann
2018-05-24 10:08         ` Kalle Valo
2018-05-12  3:57 ` Stephen Rothwell
2020-11-09  5:43 Stephen Rothwell
2020-11-10  8:43 ` Johannes Berg
2021-04-13 10:33 Stephen Rothwell
2021-04-13 10:39 ` Grumbach, Emmanuel
2021-04-13 11:32   ` Johannes Berg

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=1525851852.6910.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=toke@toke.dk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.