From: Nicholas Piggin <npiggin@gmail.com>
To: Rui Salvaterra <rsalvaterra@gmail.com>, tobias.karnat@remondis.de
Cc: linux-arch@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, sedat.dilek@gmail.com,
x86@kernel.org
Subject: Re: [PATCH] x86: enable dead code and data elimination
Date: Fri, 02 Jul 2021 10:30:02 +1000 [thread overview]
Message-ID: <1625185686.surevoro33.astroid@bobo.none> (raw)
In-Reply-To: <CALjTZvZCi07iVbEOOn8bduueRFLE3MOicWa2WFvxap+zFzpiSg@mail.gmail.com>
Excerpts from Rui Salvaterra's message of July 1, 2021 8:00 pm:
> Hi, Tobias,
>
> On Thu, 1 Jul 2021 at 10:22, <tobias.karnat@remondis.de> wrote:
>>
>> Hello,
>>
>> I have found your patch to enable x86 dead code and data elimination on the openwrt-devel mailing list and I wonder if you can sent it upstream to the kernel mailing list?
>
> As I quoted, mine is an adaptation of Nicholas Piggin's original
> patch, basically a forward-port to 5.4 (5.10 in my OpenWrt tree [1]).
> Since the original proposal has been sent upstream and hasn't been
> merged, there are probably good reasons for it (even though it works
> perfectly for my use case). Nicholas, any idea on why your original
> patch [2] hasn't been merged?
Not sure, I didn't do much testing or try too hard to get it upstream.
If you have found it works and is helpful I don't see why it couldn't
be merged. Feel free to submit it.
Thanks,
Nick
prev parent reply other threads:[~2021-07-02 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF02B93D81.2CCB21DA-ONC1258705.0032D3B2-C1258705.00338684@remondis.de>
2021-07-01 10:00 ` [PATCH] x86: enable dead code and data elimination Rui Salvaterra
2021-07-02 0:30 ` Nicholas Piggin [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=1625185686.surevoro33.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rsalvaterra@gmail.com \
--cc=sedat.dilek@gmail.com \
--cc=tobias.karnat@remondis.de \
--cc=x86@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