linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: John David Anglin <dave.anglin@bell.net>, Helge Deller <deller@gmx.de>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: Regenerate parisc defconfigs
Date: Fri, 27 Mar 2020 07:24:42 -0700	[thread overview]
Message-ID: <3b2f1736-08c0-62b3-5d1f-e34f97f06ba4@roeck-us.net> (raw)
In-Reply-To: <bcfc4d29-7b21-a3f3-8659-ee8ed369dfff@bell.net>

On 3/27/20 5:28 AM, John David Anglin wrote:
> On 2020-03-27 2:43 a.m., Guenter Roeck wrote:
>> It would be nice if there was a better way to select 32-bit
>> vs. 64-bit defconfigs (for example based on the compiler,
>> or with ARCH={parisc,parisc64}). However, that never worked
>> for parisc, so I guess we can't expect it to magically work
>> now, and much less so for a bug fix.
> LP64 is defined when using the 64-bit compiler.
> 

I know. However, as I said, parisc has never used compiler
capabilities to determine the content of defconfig.
Changing that should be done with a separate patch, if there
is interest to do so.

Guenter

  reply	other threads:[~2020-03-27 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 20:20 [PATCH] parisc: Regenerate parisc defconfigs Guenter Roeck
2020-03-26 22:19 ` Helge Deller
2020-03-26 22:47   ` James Bottomley
2020-03-26 23:01     ` Helge Deller
2020-03-27  6:43   ` Guenter Roeck
2020-03-27 12:28     ` John David Anglin
2020-03-27 14:24       ` Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-03 21:28 Helge Deller

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=3b2f1736-08c0-62b3-5d1f-e34f97f06ba4@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.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).