public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens•net>
To: Michael Neuling <mikey@neuling•org>
Cc: linuxppc-dev@ozlabs•org, mpe@ellerman•id.au,
	benh@kernel•crashing.org, imunsie@au•ibm.com
Subject: Re: [PATCH 1/4] cxl: Compile with -Werror
Date: Fri, 07 Aug 2015 13:26:07 +1000	[thread overview]
Message-ID: <1438917967.6796.3.camel@axtens.net> (raw)
In-Reply-To: <1438917941.7605.19.camel@neuling.org>

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

> Do you need to put this patch last so that you don't break bisecting the
> series?
> 
The warnings fixed in the rest of the series are from sparse, not the
compiler, so they don't break building with -Werror.

-- 
Regards,
Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 860 bytes --]

  reply	other threads:[~2015-08-07  3:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  3:18 [PATCH 1/4] cxl: Compile with -Werror Daniel Axtens
2015-08-07  3:18 ` [PATCH 2/4] cxl: sparse: Make declarations static Daniel Axtens
2015-08-07  5:48   ` Michael Neuling
2015-08-13  1:44   ` [2/4] " Michael Ellerman
2015-08-07  3:18 ` [PATCH 3/4] cxl: sparse: Flag iomem pointers properly Daniel Axtens
2015-08-07  4:13   ` Michael Neuling
2015-08-12  3:19   ` [3/4] " Michael Ellerman
2015-08-07  3:18 ` [PATCH 4/4] cxl: sparse: Silence iomem warning in debugfs file creation Daniel Axtens
2015-08-07  4:13   ` Michael Neuling
2015-08-13  1:44   ` [4/4] " Michael Ellerman
2015-08-07  3:25 ` [PATCH 1/4] cxl: Compile with -Werror Michael Neuling
2015-08-07  3:26   ` Daniel Axtens [this message]
2015-08-07  4:13 ` Michael Neuling
2015-08-13  1:44 ` [1/4] " Michael Ellerman

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=1438917967.6796.3.camel@axtens.net \
    --to=dja@axtens$(echo .)net \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=imunsie@au$(echo .)ibm.com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=mikey@neuling$(echo .)org \
    --cc=mpe@ellerman$(echo .)id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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