From: Pekka Enberg <penberg@iki.fi>
To: "Tobin C. Harding" <me@tobin.cc>, Christopher Lameter <cl@linux.com>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] slub: Do trivial comments fixes
Date: Thu, 31 Jan 2019 08:06:31 +0200 [thread overview]
Message-ID: <01ec2c57-4ece-5ee1-4d0d-d2f24695f482@iki.fi> (raw)
In-Reply-To: <20190131041003.15772-1-me@tobin.cc>
On 31/01/2019 6.10, Tobin C. Harding wrote:
> From: "Tobin C. Harding" <tobin@kernel.org>
>
> Hi Christopher,
>
> Here is a trivial patchset to wet my toes. This is my first patchset to
> mm, if there are some mm specific nuances in relation to when in the dev
> cycle (if ever) that minor (*cough* trivial) pathsets are acceptable
> please say so
>
> This patchset fixes comments strings in the SLUB subsystem.
>
> As per discussion at LCA I am working on getting my head around the SLUB
> allocator. If you specifically do *not* want me to do minor clean up
> while I'm reading please say so, I will not be offended.
For the series:
Reviewed-by: Pekka Enberg <penberg@kernel.org>
next prev parent reply other threads:[~2019-01-31 6:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:10 Tobin C. Harding
2019-01-31 4:10 ` [PATCH 1/3] slub: Fix comment spelling mistake Tobin C. Harding
2019-01-31 8:10 ` William Kucharski
2019-01-31 8:51 ` Tobin C. Harding
2019-01-31 4:10 ` [PATCH 2/3] slub: Capitialize comment string Tobin C. Harding
2019-01-31 4:10 ` [PATCH 3/3] slub: Use C89 comment style Tobin C. Harding
2019-01-31 6:06 ` Pekka Enberg [this message]
2019-01-31 8:52 ` [PATCH 0/3] slub: Do trivial comments fixes Tobin C. Harding
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=01ec2c57-4ece-5ee1-4d0d-d2f24695f482@iki.fi \
--to=penberg@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=me@tobin.cc \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tobin@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
all inboxes | Powered by JetHome®