From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Guenter Roeck <linux@roeck-us.net>,
Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Balbir Singh <bsingharora@gmail.com>,
Daniel Axtens <dja@axtens.net>,
Paul Mackerras <paulus@ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: Linux 5.19-rc6
Date: Wed, 13 Jul 2022 22:50:06 +0100 [thread overview]
Message-ID: <CADVatmPx=T_i1oaX2i_d5crbWkixFZU7s-_wky_kz58wDgwGDQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wgUGp96_Wup3=Utws=Mn+07vi7ZXknv4nKZkAJv8Ezhnw@mail.gmail.com>
On Wed, Jul 13, 2022 at 10:45 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Wed, Jul 13, 2022 at 2:36 PM Sudip Mukherjee
> <sudipm.mukherjee@gmail.com> wrote:
> >
> > > >
> > > > https://lore.kernel.org/all/20220524025139.40212-1-wangkefeng.wang@huawei.com/
> > >
> > > That patch looks sane to me, but I guess Guenter would need to check
> >
> > I still see the failure in my builds with this patch. But surprisingly
> > I dont see the build failure (with or without this patch) with gcc-12,
> > only with gcc-11.
>
> Arrghs. "build failure"?
Uhh.. no, sorry.. I meant the same problem which Guenter reported with
powerpc64-linux-ld, hard float and soft float.
But I dont see this problem with gcc-12, only with gcc-11.
--
Regards
Sudip
next prev parent reply other threads:[~2022-07-13 21:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 21:54 Linux 5.19-rc6 Linus Torvalds
2022-07-11 6:44 ` Build regressions/improvements in v5.19-rc6 Geert Uytterhoeven
2022-07-13 5:07 ` Linux 5.19-rc6 Guenter Roeck
2022-07-13 19:36 ` Linus Torvalds
2022-07-13 19:48 ` Russell King (Oracle)
2022-07-13 20:21 ` Linus Torvalds
2022-07-13 20:40 ` Guenter Roeck
2022-07-13 20:42 ` Linus Torvalds
2022-07-14 12:20 ` Russell King (Oracle)
2022-07-14 12:14 ` Russell King (Oracle)
2022-07-13 21:36 ` Sudip Mukherjee
2022-07-13 21:45 ` Linus Torvalds
2022-07-13 21:50 ` Sudip Mukherjee [this message]
2022-07-13 22:56 ` Guenter Roeck
2022-07-13 23:09 ` Sudip Mukherjee
2022-07-13 23:12 ` Guenter Roeck
2022-07-13 23:26 ` Sudip Mukherjee
2022-07-13 23:44 ` Guenter Roeck
2022-07-13 23:02 ` Guenter Roeck
2022-07-14 1:30 ` Kefeng Wang
2022-07-13 19:53 ` Alex Deucher
2022-07-13 20:22 ` Linus Torvalds
2022-07-13 20:45 ` Guenter Roeck
2022-07-13 20:46 ` Guenter Roeck
2022-07-13 20:50 ` Linus Torvalds
2022-07-13 21:00 ` Alex Deucher
2022-07-13 21:32 ` Linus Torvalds
2022-07-14 7:23 ` Geert Uytterhoeven
2022-07-14 13:20 ` Guenter Roeck
2022-07-14 13:56 ` Geert Uytterhoeven
2022-07-14 16:48 ` Linus Torvalds
2022-07-14 17:24 ` Guenter Roeck
2022-07-14 17:37 ` Linus Torvalds
2022-07-15 7:26 ` Geert Uytterhoeven
2022-07-14 16:52 ` Alex Deucher
2022-07-14 23:16 ` Russell Currey
2022-07-15 9:33 ` Sudip Mukherjee
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='CADVatmPx=T_i1oaX2i_d5crbWkixFZU7s-_wky_kz58wDgwGDQ@mail.gmail.com' \
--to=sudipm.mukherjee@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bsingharora@gmail.com \
--cc=dja@axtens.net \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.org \
--cc=sunpeng.li@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=wangkefeng.wang@huawei.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).