From: Linus Walleij <linus.walleij@linaro.org>
To: "Aiqun(Maria) Yu" <quic_aiquny@quicinc.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Chester Lin <clin@suse.com>
Subject: Re: [GIT PULL] Pin control fixes for v6.7
Date: Fri, 1 Dec 2023 09:12:23 +0100 [thread overview]
Message-ID: <CACRpkdYcPBSp-XGXr=3a+AGOVVVHQoaciSgAUuJS+=3ScGWcSg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZtCxwLZCY4autrTvonmZ3XcVzH6iXqXanS97VKCZ+ERw@mail.gmail.com>
On Fri, Dec 1, 2023 at 9:10 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> Hi Nathan, Nick,
>
> (just picking some LLVM compiler people I know of... and trust)
Forget that part of the mail, written out-of-context when I was
running different
disassembly of GCC vs LLVM code. I figured it out and concluded that
the compilers
are fine and doing the right thing, it's a none-issue in that regard.
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-12-01 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 12:09 [GIT PULL] Pin control fixes for v6.7 Linus Walleij
2023-11-29 14:55 ` Linus Torvalds
2023-11-29 15:08 ` Linus Walleij
2023-11-30 5:37 ` Aiqun(Maria) Yu
2023-12-01 8:10 ` Linus Walleij
2023-12-01 8:12 ` Linus Walleij [this message]
2023-12-01 10:06 ` Aiqun(Maria) Yu
2023-12-01 15:34 ` Aiqun(Maria) Yu
2023-11-29 15:47 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 22:50 [GIT PULL] pin " Linus Walleij
2023-12-22 0:58 ` pr-tracker-bot
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='CACRpkdYcPBSp-XGXr=3a+AGOVVVHQoaciSgAUuJS+=3ScGWcSg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=clin@suse.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_aiquny@quicinc.com \
--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).