From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Rudraksha Gupta <guptarud@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, torvalds@linux-foundation.org,
"Ben Wolsieffer" <ben.wolsieffer@hefring.com>,
"Naresh Kamboju" <naresh.kamboju@linaro.org>,
"Christian Schrrefl" <chrisi.schrefl@gmail.com>,
"Russell King" <rmk+kernel@armlinux.org.uk>,
"Ard Biesheuvel" <ardb@kernel.org>,
anders.roxell@linaro.org, arnd@arndb.de,
dan.carpenter@linaro.org, laura.nao@collabora.com,
lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
"Nick Clifton" <nickc@redhat.com>,
"Richard Earnshaw" <richard.earnshaw@arm.com>,
"Ramana Radhakrishnan" <ramanara@nvidia.com>,
"Linux Kernel Functional Testing" <lkft@linaro.org>
Subject: Re: [PATCH v2] arm: Fix rustgcc unknown argument '-mno-fdpic'
Date: Thu, 22 May 2025 15:48:50 +0200 [thread overview]
Message-ID: <CANiq72n3UzgG4BTcZXd9aJK_9+BwodRkbzewPtipi4-iCqdeqA@mail.gmail.com> (raw)
In-Reply-To: <db93019f-0a57-4b1d-95a6-ed5a6ab9a989@gmail.com>
On Thu, May 22, 2025 at 3:27 PM Rudraksha Gupta <guptarud@gmail.com> wrote:
>
> Thanks! :D Happy to send in a v3 if needed
No worries, I will apply this one :)
I will remove the tag, unless you want it there for some reason (e.g.
because you want to point out some extra testing that goes beyond what
would normally be done).
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-05-22 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 12:02 [PATCH v2] arm: Fix rustgcc unknown argument '-mno-fdpic' Rudraksha Gupta
2025-05-22 12:52 ` Miguel Ojeda
2025-05-22 13:27 ` Rudraksha Gupta
2025-05-22 13:48 ` Miguel Ojeda [this message]
2025-05-22 15:14 ` Rudraksha Gupta
2025-05-22 22:13 ` Miguel Ojeda
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=CANiq72n3UzgG4BTcZXd9aJK_9+BwodRkbzewPtipi4-iCqdeqA@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=anders.roxell@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=ben.wolsieffer@hefring.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chrisi.schrefl@gmail.com \
--cc=dakr@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=gary@garyguo.net \
--cc=guptarud@gmail.com \
--cc=justinstitt@google.com \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nickc@redhat.com \
--cc=ojeda@kernel.org \
--cc=ramanara@nvidia.com \
--cc=regressions@lists.linux.dev \
--cc=richard.earnshaw@arm.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).