From: Russell Currey <ruscur@russell.cc>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerc: Update asm-prototypes.h comment
Date: Wed, 22 Jun 2022 18:32:04 +1000 [thread overview]
Message-ID: <da25a411031208310b63dd652a9ae5a2e65c037a.camel@russell.cc> (raw)
In-Reply-To: <20220617080243.2177583-1-mpe@ellerman.id.au>
On Fri, 2022-06-17 at 18:02 +1000, Michael Ellerman wrote:
> This header was recently cleaned up in commit 76222808fc25 ("powerpc:
> Move C prototypes out of asm-prototypes.h"), update the comment to
> reflect it's proper purpose.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Hi Michael, subject says "powerc" instead of "powerpc".
- clippy
next prev parent reply other threads:[~2022-06-22 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:02 [PATCH] powerc: Update asm-prototypes.h comment Michael Ellerman
2022-06-22 8:32 ` Russell Currey [this message]
2022-06-22 10:07 ` Michael Ellerman
2022-06-29 12:15 ` Michael Ellerman
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=da25a411031208310b63dd652a9ae5a2e65c037a.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).