All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-parisc@vger.kernel.org, Helge Deller <deller@gmx.de>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>
Subject: Re: Linux 3.15-rc6
Date: Thu, 22 May 2014 10:20:32 -0700	[thread overview]
Message-ID: <20140522172032.GA20975@roeck-us.net> (raw)
In-Reply-To: <CA+55aFzwqPh+WUAxi2CY8D6k+LkDbUb__G98qVFrE-DHNMSPUw@mail.gmail.com>

On Thu, May 22, 2014 at 07:47:35AM +0900, Linus Torvalds wrote:
> Due to travels and related lack of internet access, the rc releases
> haven't been following the normal Sunday release cycle, and since I
> caught up with what happened while I was off-line, rather than wait
> until next Sunday to reset to the normal cycle, I'm just releasing rc6
> now mid-week from Tokyo.
> 
> With rc5 being a couple of days early, and rc6 being several days
> late, we had almost two weeks in between them. The size of the result
> is not twice as large, though, hopefully partially because it's
> getting late in the rc series and things are supposed to be calming
> down, but presumably also because some submaintainers just didn't send
> their pull requests because they knew I was off-line. Whatever the
> reason, things don't look bad.
> 
> The patch distribution looks pretty normal too. Mostly drivers (acpi,
> sound, media, i915, clk, pci..) with the bulk of the rest being
> various arch updates (notably MIPS, but arm and parisc too). And a
> smattering of other random stuff in filesystems and core kernel code.
> 
Unfortunately it appears that the parisc changes cause build failures
with parisc 64 bit builds.

Building parisc:a500_defconfig ... failed
Building parisc:generic-64bit_defconfig ... failed

Error log:
arch/parisc/kernel/built-in.o: In function `sys_call_table':
(.rodata+0xad0): undefined reference to `compat_sys_renameat2'
make: *** [vmlinux] Error 1

parisc 32 bit builds (defconfig and generic-32bit_defconfig) are fine.

Guenter

  reply	other threads:[~2014-05-22 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 22:47 Linux 3.15-rc6 Linus Torvalds
2014-05-22 17:20 ` Guenter Roeck [this message]
2014-05-23  0:43   ` Linus Torvalds
2014-05-23  1:07     ` Guenter Roeck
2014-05-23  1:27       ` Linus Torvalds
2014-05-23  9:12         ` Miklos Szeredi
2014-05-23  9:16           ` Helge Deller

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=20140522172032.GA20975@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=deller@gmx.de \
    --cc=jejb@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.