From: Richard Weinberger <richard.weinberger@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Richard Weinberger <richard@nod.at>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/15 v2] UBIFS: improve function-level documentation
Date: Wed, 5 Oct 2016 23:40:04 +0200 [thread overview]
Message-ID: <CAFLxGvxHuosxhrwW0N63jJOatpn3nNE79o_UqBkdUWRepUNfaA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1610012252190.3445@hadrien>
On Sat, Oct 1, 2016 at 10:53 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> Fix various inconsistencies in the documentation associated with various
> functions.
>
> In the case of fs/ubifs/lprops.c, the second parameter of
> ubifs_get_lp_stats was renamed from st to lst in commit 84abf972ccff
> ("UBIFS: add re-mount debugging checks")
>
> In the case of fs/ubifs/lpt_commit.c, the excess variables have never
> existed in the associated functions since the code was introduced into the
> kernel.
>
> The others appear to be straightforward typos.
>
> Issues detected using Coccinelle (http://coccinelle.lip6.fr/)
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Applied, thanks.
--
Thanks,
//richard
prev parent reply other threads:[~2016-10-05 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 20:53 [PATCH 01/15 v2] UBIFS: improve function-level documentation Julia Lawall
2016-10-05 21:40 ` Richard Weinberger [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=CAFLxGvxHuosxhrwW0N63jJOatpn3nNE79o_UqBkdUWRepUNfaA@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).