public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Arnd Bergmann <arnd@arndb•de>
Cc: linaro-kernel@lists•linaro.org,
	kernel-build-reports@lists•linaro.org,
	linux-next@vger•kernel.org,
	"linus.walleij@linaro•org" <linus.walleij@linaro•org>,
	linux-arm-kernel@lists•infradead.org,
	linux-kernel@vger•kernel.org
Subject: Re: next-20151221 build: 2 failures 13 warnings (next-20151221)
Date: Mon, 21 Dec 2015 15:41:49 +0000	[thread overview]
Message-ID: <20151221154149.GK5727@sirena.org.uk> (raw)
In-Reply-To: <201512211505.34074.arnd@arndb.de>

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

On Mon, Dec 21, 2015 at 03:05:33PM +0100, Arnd Bergmann wrote:

Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns.  Doing this makes your messages much
easier to read and reply to.

> Just looking at the remaining warnings/errors in linux-next:

> > Warnings:
> >         <stdin>:1307:2: warning: #warning syscall copy_file_range not implemented [-Wcpp]

> Not sure how we can improve this, the same thing seems to happen every time a new syscall gets
> introduced. The actual change is trivial, but we need a better method to sync all architectures.

Now we've got the warning count down sufficiently the autobuilders may
actually be just fine here.

> > arm-multi_v7_defconfig : PASS, 0 errors, 8 warnings, 0 section mismatches

> > Warnings:
> >         arch/arm/configs/multi_v7_defconfig:433:warning: symbol value 'm' invalid for MFD_DA9063

> I need to look into this, probably the result of a defconfig change we merged, but it's not
> clear whether the driver should be a module, or the defconfig should have it built-in.

The driver should at least support building modularly, there was a patch
sent to MFD IIRC but I guess it's not applied yet (Lee is on vacation I
believe which probably won't help).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-12-21 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 11:34 next-20151221 build: 2 failures 13 warnings (next-20151221) Build bot for Mark Brown
2015-12-21 14:05 ` Arnd Bergmann
2015-12-21 15:41   ` Mark Brown [this message]

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=20151221154149.GK5727@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=arnd@arndb$(echo .)de \
    --cc=kernel-build-reports@lists$(echo .)linaro.org \
    --cc=linaro-kernel@lists$(echo .)linaro.org \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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