From: Arnd Bergmann <arnd@arndb.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Joseph Myers <joseph@codesourcery.com>,
David Howells <dhowells@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] making uapi/linux/elfcore.h useful again
Date: Fri, 14 Sep 2018 21:55:21 +0200 [thread overview]
Message-ID: <CAK8P3a03qF4+yGBNVLymrSRN7QjDGjnpduoPwnprwv+kfHZ0Cg@mail.gmail.com> (raw)
In-Reply-To: <20180914174528.GA35000@gmail.com>
On Fri, Sep 14, 2018 at 7:45 PM Ingo Molnar <mingo@kernel.org> wrote:
> * Arnd Bergmann <arnd@arndb.de> wrote:
> > - Move required data from the private x86 asm/elf.h file into
> > a new uapi/asm/elf.h. Some other architectures already do that,
> > but most of them do not. Before applying the patch, we have
> > to do this for all architectures
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
> I suspect this wants to go through -mm, or do you want to carry it?
-mm is probably best. For now, I just want to see if there are any
concerns about this, and then I'd have to do the full version that
changes all architectures.
Arnd
next prev parent reply other threads:[~2018-09-14 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 11:38 [PATCH] [RFC] making uapi/linux/elfcore.h useful again Arnd Bergmann
2018-09-14 17:45 ` Ingo Molnar
2018-09-14 19:55 ` Arnd Bergmann [this message]
2018-09-15 11:37 ` Ingo Molnar
2018-09-17 12:05 ` Joseph Myers
2018-09-18 14:21 ` Arnd Bergmann
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=CAK8P3a03qF4+yGBNVLymrSRN7QjDGjnpduoPwnprwv+kfHZ0Cg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).