From: Palmer Dabbelt <palmer@dabbelt.com>
To: rostedt@goodmis.org
Cc: colin.king@canonical.com, guoren@kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
linux-csky@vger.kernel.org, linux-riscv@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: Fix spelling mistake "disabed" -> "disabled"
Date: Mon, 29 Mar 2021 22:54:19 -0700 (PDT) [thread overview]
Message-ID: <mhng-54032ff9-fc8d-48fb-87a0-ff075313d077@palmerdabbelt-glaptop> (raw)
In-Reply-To: <20210317094223.34797d5d@gandalf.local.home>
On Wed, 17 Mar 2021 06:42:23 PDT (-0700), rostedt@goodmis.org wrote:
> On Tue, 16 Mar 2021 21:21:08 -0700 (PDT)
> Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
>> Thanks, this is on fixes.
>
> What does this mean? Is there a tree that spelling fixes go through now?
>
> I had already pulled this patch into my queue for the next merge window
> (and it's still in the testing phase with other patches before going to
> linux-next).
>
> Should I drop it?
Oh, sorry. It's on the fixes branch of the riscv tree
<https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git> .
It's what I sent up to Linus every week, this one already went up.
I must have not been looking closely enough, for some reason I thought
this only touched the riscv tree. I wouldn't have taken it without an
Ack if I'd noticed, I guess just because it was only a comment spelling
change I hadn't checked the paths. I'll try not to do that again.
prev parent reply other threads:[~2021-03-30 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 9:40 [PATCH] ftrace: Fix spelling mistake "disabed" -> "disabled" Colin King
2021-03-17 4:21 ` Palmer Dabbelt
2021-03-17 13:42 ` Steven Rostedt
2021-03-30 5:54 ` Palmer Dabbelt [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=mhng-54032ff9-fc8d-48fb-87a0-ff075313d077@palmerdabbelt-glaptop \
--to=palmer@dabbelt.com \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=colin.king@canonical.com \
--cc=guoren@kernel.org \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).