From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/time: use feature fixup in __USE_RTC() instead of cpu feature.
Date: Mon, 26 Aug 2019 07:06:50 -0500 [thread overview]
Message-ID: <20190826120650.GR31406@gate.crashing.org> (raw)
In-Reply-To: <87blwc40i4.fsf@concordia.ellerman.id.au>
On Mon, Aug 26, 2019 at 09:41:39PM +1000, Michael Ellerman wrote:
> Given how many 601 users there are, maybe 1?, I think that would be a
> simpler option and avoids complicating the code / binary for everyone
> else.
Or you could remove 601 support altogether?
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/time: use feature fixup in __USE_RTC() instead of cpu feature.
Date: Mon, 26 Aug 2019 07:06:50 -0500 [thread overview]
Message-ID: <20190826120650.GR31406@gate.crashing.org> (raw)
In-Reply-To: <87blwc40i4.fsf@concordia.ellerman.id.au>
On Mon, Aug 26, 2019 at 09:41:39PM +1000, Michael Ellerman wrote:
> Given how many 601 users there are, maybe 1?, I think that would be a
> simpler option and avoids complicating the code / binary for everyone
> else.
Or you could remove 601 support altogether?
Segher
next prev parent reply other threads:[~2019-08-26 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 6:59 [PATCH] powerpc/time: use feature fixup in __USE_RTC() instead of cpu feature Christophe Leroy
2019-08-26 6:59 ` Christophe Leroy
2019-08-26 11:41 ` Michael Ellerman
2019-08-26 11:41 ` Michael Ellerman
2019-08-26 11:48 ` Christophe Leroy
2019-08-26 11:48 ` Christophe Leroy
2019-08-27 2:13 ` Michael Ellerman
2019-08-27 2:13 ` Michael Ellerman
2019-08-26 12:06 ` Segher Boessenkool [this message]
2019-08-26 12:06 ` Segher Boessenkool
2019-08-26 13:25 ` Benjamin Herrenschmidt
2019-08-26 13:25 ` Benjamin Herrenschmidt
2019-08-26 13:40 ` Christophe Leroy
2019-08-26 13:40 ` Christophe Leroy
2019-08-27 2:12 ` Michael Ellerman
2019-08-27 2:12 ` Michael Ellerman
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=20190826120650.GR31406@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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 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.