From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: linux-xfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: Correct comment tyops -> typos
Date: Thu, 7 Nov 2019 14:03:06 -0800 [thread overview]
Message-ID: <20191107220306.GI6219@magnolia> (raw)
In-Reply-To: <e8187485a6ee7fffef738f90cddfa052ccdb927c.camel@perches.com>
On Thu, Nov 07, 2019 at 01:56:13PM -0800, Joe Perches wrote:
> On Thu, 2019-11-07 at 13:25 -0800, Darrick J. Wong wrote:
> > On Wed, Nov 06, 2019 at 10:01:15PM -0800, Joe Perches wrote:
> > > Just fix the typos checkpatch notices...
> > >
> > > Signed-off-by: Joe Perches <joe@perches.com>
> >
> > Looks ok,
> > Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
>
> Darrick? You are the listed maintainer here.
> Are you applying this or just reviewing it?
Applying it, though there's another 50+ patches to go...
--D
>
>
prev parent reply other threads:[~2019-11-07 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 6:01 [PATCH] xfs: Correct comment tyops -> typos Joe Perches
2019-11-07 15:53 ` Bill O'Donnell
2019-11-07 21:25 ` Darrick J. Wong
2019-11-07 21:56 ` Joe Perches
2019-11-07 22:03 ` Darrick J. Wong [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=20191107220306.GI6219@magnolia \
--to=darrick.wong@oracle.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.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