public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	Nicholas Mc Guire <der.herr@hofr.at>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: RFC arch/sh/kernel/traps_64.c - unclear if/else construct (hpux compat layer)
Date: Tue, 17 Feb 2015 16:15:11 +0100	[thread overview]
Message-ID: <54E35AFF.3030206@gmx.de> (raw)
In-Reply-To: <1424162967.7082.7.camel@x220>

H Paul,

On 17.02.2015 09:49, Paul Bolle wrote:
> On Mon, 2015-02-16 at 22:24 +0100, Helge Deller wrote:
>> The hpux code is broken anyway.
>> I'm going to remove it from the tree.
>
> That happened in commit 04c161497716 ("parisc: hpux - Drop support for
> HP-UX binaries"), which is included in today's linux-next
> (next-20150217).

Yes.

> That commit removed the Kconfig symbol HPUX. As a result BINFMT_SOM (see
> fs/Kconfig.binfmt) can't be set anymore. I assume a patch to remove that
> symbol too is also part of that series. Is that correct?

I missed it, but just sent out a patch to remove BINFMT_SOM too.
It will be in the next linux-next tree via
http://git.kernel.org/cgit/linux/kernel/git/deller/parisc-linux.git/log/?h=for-next

Helge


      reply	other threads:[~2015-02-17 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  9:37 RFC arch/sh/kernel/traps_64.c - unclear if/else construct Nicholas Mc Guire
2015-02-16 21:24 ` RFC arch/sh/kernel/traps_64.c - unclear if/else construct (hpux compat layer) Helge Deller
2015-02-17  8:49   ` Paul Bolle
2015-02-17 15:15     ` Helge Deller [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=54E35AFF.3030206@gmx.de \
    --to=deller@gmx.de \
    --cc=dan.carpenter@oracle.com \
    --cc=der.herr@hofr.at \
    --cc=jejb@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=valentinrothberg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox