mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-arch@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au,
	linux-kernel@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: USE_ELF_CORE_DUMP?
Date: Fri, 24 Apr 2009 09:17:26 +0200	[thread overview]
Message-ID: <49F16786.7010401@petalogix.com> (raw)
In-Reply-To: <20090423183331.GA19899@lst.de>

Christoph Hellwig wrote:
> Currently all architectures but microblaze unconditionally define
> USE_ELF_CORE_DUMP.  The microblaze ommision seems like an error to
> me, so can we just kill this ifdef and make sure we are the same
> everywhere?
>   
Where did you find it?
I haven't seen in in mainline (noMMU kernel). It is in my MMU patches
which I want to send for review soon.

For noMMU I use CONFIG_BINFMT_FLAT (binfmt_flat.c) where I don't need
USE_ELF_CORE_DUMP
For MMU I use CONFIG_BINFMT_ELF (binfmt_elf.c) where USE_ELF_CORE_DUMP
make sense to me.

Can you give me some clue what you are trying to fix?

Thanks,
Michal


> --
> To unsubscribe from this list: send the line "unsubscribe linux-arch" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663


  parent reply	other threads:[~2009-04-24  7:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 18:33 USE_ELF_CORE_DUMP? Christoph Hellwig
2009-04-23 18:48 ` USE_ELF_CORE_DUMP? Matthew Wilcox
2009-04-24  7:17 ` Michal Simek [this message]
2009-04-26  9:21   ` USE_ELF_CORE_DUMP? Christoph Hellwig
2009-09-26 19:50   ` [PATCH] kill USE_ELF_CORE_DUMP Christoph Hellwig
2009-09-26 20:03     ` Hugh Dickins
2009-09-29 12:05     ` Ralf Baechle

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=49F16786.7010401@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=hch@lst.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    /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

Powered by JetHome