linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wireless <linux-wireless@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sara Sharon <sara.sharon@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>,
	Kees Cook <keescook@google.com>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: linux-next: build warnings after merge of the wireless-drivers-next tree
Date: Fri, 30 Nov 2018 09:43:21 +0200	[thread overview]
Message-ID: <87h8fz57ty.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20181130165006.60b2545f@canb.auug.org.au> (Stephen Rothwell's message of "Fri, 30 Nov 2018 16:50:06 +1100")

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi Kalle,
>
> On Fri, 30 Nov 2018 06:33:47 +0200 Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> I take it that -Wimplict-fallthrough is not enabled by default yet? So
>> Dave and Linus won't see these warnings?
>
> Correct.
>
>> What I'm planning is to send a pull request to Dave today and fix these
>> warnings in the next pull request. Does that sound good?
>
> That sounds fine.

Great, thanks for the confirmation. I'll then send the pull request
today.

-- 
Kalle Valo

  reply	other threads:[~2018-11-30  7:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30  1:05 linux-next: build warnings after merge of the wireless-drivers-next tree Stephen Rothwell
2018-11-30  4:33 ` Kalle Valo
2018-11-30  5:50   ` Stephen Rothwell
2018-11-30  7:43     ` Kalle Valo [this message]
2018-12-03 12:38       ` Luciano Coelho
     [not found]         ` <1773a3329bcd1bde2a22c267e4c582b0149a307e.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-12-03 15:15           ` Gustavo A. R. Silva
2018-12-19  2:47 ` Stephen Rothwell
2018-12-19  7:51   ` Kalle Valo
2018-12-19  8:31     ` Grumbach, Emmanuel
     [not found]       ` <0BA3FCBA62E2DC44AF3030971E174FB3013375F96C-cNwSTNrqBuVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2018-12-19 10:27         ` Luca Coelho
2018-12-19 12:40       ` Kalle Valo

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=87h8fz57ty.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=gustavo@embeddedor.com \
    --cc=keescook@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=sara.sharon@intel.com \
    --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).