From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christina Quast <cquast@hanoverdisplays.com>
Cc: trivial@kernel.org, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs: kernfs: Corrected spelling mistake
Date: Tue, 02 Apr 2019 08:45:38 -0700 [thread overview]
Message-ID: <f7604a4d2794ec37d7043b56851f03b18501f9cd.camel@perches.com> (raw)
In-Reply-To: <20190402130827.GA32338@kroah.com>
On Tue, 2019-04-02 at 15:08 +0200, Greg Kroah-Hartman wrote:
> Remember, kernel maintainers have the short term memory of a squirrel :)
^ some
prev parent reply other threads:[~2019-04-02 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 11:44 [PATCH] fs: kernfs: Corrected spelling mistake Christina Quast
2019-04-02 11:58 ` Mukesh Ojha
2019-04-02 12:00 ` Greg Kroah-Hartman
2019-04-02 12:27 ` [PATCH v2] " Christina Quast
2019-04-02 13:08 ` Greg Kroah-Hartman
2019-04-02 14:01 ` Christina Quast
2019-04-02 15:45 ` Joe Perches [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=f7604a4d2794ec37d7043b56851f03b18501f9cd.camel@perches.com \
--to=joe@perches.com \
--cc=cquast@hanoverdisplays.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=trivial@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).