From: Max Filippov <jcmvbkbc@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Chris Zankel <chris@zankel.net>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@linux-xtensa.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xtensa: remove unneeded BITS_PER_LONG define
Date: Thu, 27 Jun 2019 13:37:17 -0700 [thread overview]
Message-ID: <CAMo8BfJe6va+=oB_VWG5F0xWFQv+Qbx5DXdjJbO2XLNh5rs3=g@mail.gmail.com> (raw)
In-Reply-To: <20190627070052.8647-1-yamada.masahiro@socionext.com>
Hi Yamada-san,
On Thu, Jun 27, 2019 at 12:01 AM Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
>
> Xtensa does not define CONFIG_64BIT. The generic definition in
> include/asm-generic/bitsperlong.h should work.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> arch/xtensa/include/asm/types.h | 8 --------
> 1 file changed, 8 deletions(-)
After this change the file arch/xtensa/include/asm/types.h is effectively
empty, only including uapi/asm/types.h. Maybe it should be dropped
altogether?
--
Thanks.
-- Max
prev parent reply other threads:[~2019-06-27 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 7:00 [PATCH] xtensa: remove unneeded BITS_PER_LONG define Masahiro Yamada
2019-06-27 20:37 ` Max Filippov [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='CAMo8BfJe6va+=oB_VWG5F0xWFQv+Qbx5DXdjJbO2XLNh5rs3=g@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).