From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: Build failures in v3.10-stable-queue, v3.14-stable-queue
Date: Wed, 27 Jan 2016 09:42:11 -0800 [thread overview]
Message-ID: <20160127174211.GB2746@kroah.com> (raw)
In-Reply-To: <56A8B68F.107@roeck-us.net>
On Wed, Jan 27, 2016 at 04:22:39AM -0800, Guenter Roeck wrote:
> ---
> mn10300 (v3.10, v3.14):
>
> kernel/uid16.c:19:1: error: unknown type name 'old_uid_t'
> kernel/uid16.c:19:1: error: unknown type name 'old_gid_t'
> ipc/util.c:609:2: error: 'old_uid_t' undeclared
>
> and other similar errors. Requires c86576ea114a ("mn10300: Select CONFIG_HAVE_UID16
> to fix build failure"). Results in minor easy to resolve conflict in v3.10.y (I didn't
> check v3.14.y). Let me know if you need a backport.
Now queued up for all of these, the conflict was easy to fix, thanks.
greg k-h
prev parent reply other threads:[~2016-01-27 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 12:22 Build failures in v3.10-stable-queue, v3.14-stable-queue Guenter Roeck
2016-01-27 12:31 ` Will Deacon
2016-01-27 17:39 ` Greg Kroah-Hartman
2016-01-27 13:27 ` Nicolas Dichtel
2016-01-27 15:48 ` Greg Kroah-Hartman
2016-01-27 16:34 ` Build failures in v3.10-stable-queue, v3.14-stable-queue (+4.1, 4.3, 4.4) Guenter Roeck
2016-01-27 16:37 ` Will Deacon
2016-01-27 17:16 ` Guenter Roeck
2016-01-27 17:49 ` Greg Kroah-Hartman
2016-01-28 9:38 ` Will Deacon
2016-01-28 15:49 ` Sudeep Holla
2016-01-31 19:22 ` Greg Kroah-Hartman
2016-01-27 17:20 ` Build failures in v3.10-stable-queue, v3.14-stable-queue Greg Kroah-Hartman
2016-01-27 17:42 ` Greg Kroah-Hartman [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=20160127174211.GB2746@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.com \
/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.