From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: "Hans-Christian Egtvedt" <hans-christian.egtvedt@atmel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH v2] avr32: Fix build failure conflicting types for 'sys_execve'
Date: Sun, 12 Dec 2010 20:37:58 +0100 [thread overview]
Message-ID: <201012122037.59016.PeterHuewe@gmx.de> (raw)
In-Reply-To: <1291976741.18008.37.camel@hcegtvedt>
Am Freitag 10 Dezember 2010, 11:25:41 schrieb Hans-Christian Egtvedt:
> Nack, I've piped up a patch in
> http://git.kernel.org/?p=linux/kernel/git/egtvedt/avr32-2.6.git;a=shortlog;
> h=refs/heads/next that does this and more. The syscalls.h header file needs
> a bit more cleanup.
>
> I'll also notify stable to get it backported. Do you have an idea how
> far back it should go?
Hi,
Linus' tree fails since August 19th due to this issue, so it falls into the
2.6.36 merge window only.
http://kisskb.ellerman.id.au/kisskb/buildresult/3059836/
(but it still failed for quite a while longer due to other issues ;)
Thanks,
Peter
(a reported by on the patch would have been nice ;)
next prev parent reply other threads:[~2010-12-12 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 23:19 [PATCH] avr32: Fix build failure conflicting types for 'sys_execve' Peter Huewe
2010-12-09 7:54 ` Hans-Christian Egtvedt
2010-12-09 18:21 ` [stable] " Greg KH
2010-12-09 18:42 ` Peter Hüwe
2010-12-09 19:13 ` Greg KH
2010-12-09 21:15 ` [PATCH v2] " Peter Huewe
2010-12-10 10:25 ` Hans-Christian Egtvedt
2010-12-12 19:37 ` Peter Hüwe [this message]
2010-12-13 8:12 ` Hans-Christian Egtvedt
2010-12-13 17:12 ` Peter Hüwe
2010-12-13 17:27 ` Hans-Christian Egtvedt
2010-12-10 15:58 ` [PATCH] " David Howells
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=201012122037.59016.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=hans-christian.egtvedt@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.