From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>,
Tony Ambardar <tony.ambardar@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
Tony Ambardar <Tony.Ambardar@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Stable <stable@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Rosen Penev <rosenp@gmail.com>
Subject: Re: [PATCH v3] powerpc: fix EDEADLOCK redefinition error in uapi/asm/errno.h
Date: Mon, 19 Apr 2021 14:00:07 +1000 [thread overview]
Message-ID: <161880480720.1398509.14927712402293166726.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200917135437.1238787-1-Tony.Ambardar@gmail.com>
On Thu, 17 Sep 2020 06:54:37 -0700, Tony Ambardar wrote:
> A few archs like powerpc have different errno.h values for macros
> EDEADLOCK and EDEADLK. In code including both libc and linux versions of
> errno.h, this can result in multiple definitions of EDEADLOCK in the
> include chain. Definitions to the same value (e.g. seen with mips) do
> not raise warnings, but on powerpc there are redefinitions changing the
> value, which raise warnings and errors (if using "-Werror").
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: fix EDEADLOCK redefinition error in uapi/asm/errno.h
https://git.kernel.org/powerpc/c/7de21e679e6a789f3729e8402bc440b623a28eae
cheers
prev parent reply other threads:[~2021-04-19 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 7:42 [PATCH v1] powerpc: fix EDEADLOCK redefinition error in uapi/asm/errno.h Tony Ambardar
2020-09-17 0:07 ` [PATCH v2] " Tony Ambardar
2020-09-17 11:55 ` Michael Ellerman
2020-09-17 13:42 ` Tony Ambardar
2020-09-17 14:01 ` Arnd Bergmann
[not found] ` <CAK8P3a3FVoDzNb1TOA6cRQDdEc+st7KkBL70t0FeStEziQG4+A__37056.5000850306$1600351707$gmane$org@mail.gmail.com>
2020-09-17 14:34 ` Andreas Schwab
2020-09-19 4:15 ` Tony Ambardar
2020-09-17 13:54 ` [PATCH v3] " Tony Ambardar
2021-04-16 4:34 ` Tony Ambardar
2021-04-16 10:41 ` Michael Ellerman
2021-04-17 1:00 ` Tony Ambardar
2021-04-19 4:00 ` Michael Ellerman [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=161880480720.1398509.14927712402293166726.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bpf@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rosenp@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tony.ambardar@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;
as well as URLs for NNTP newsgroup(s).