From: xiaolei li <xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>
Cc: boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH 0/2] Fix some function description mismatches
Date: Thu, 29 Mar 2018 09:07:29 +0800 [thread overview]
Message-ID: <1522285649.8261.5.camel@mhfsdcap03> (raw)
In-Reply-To: <24567439.icTe1ItB9o@blindfold>
Hi Richard
On Wed, 2018-03-28 at 14:06 +0200, Richard Weinberger wrote:
> Am Mittwoch, 28. März 2018, 11:13:56 CEST schrieb Xiaolei Li:
> > This patch fixes some function description mismatches.
>
> Did you find these manually or in some automated way?
I found these by accident. Do you know whether there is a tool to do
comments check?
Thanks.
Xiaolei
>
> Thanks,
> //richard
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2018-03-29 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 9:13 [PATCH 0/2] Fix some function description mismatches Xiaolei Li
[not found] ` <1522228438-64034-1-git-send-email-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-03-28 9:13 ` [PATCH 1/2] mtd: Fix some function description mismatches in mtdcore.c Xiaolei Li
2018-03-28 9:13 ` [PATCH 2/2] mtd: nand: Fix some function description mismatches in core.c Xiaolei Li
[not found] ` <1522228438-64034-3-git-send-email-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-03-28 11:37 ` Boris Brezillon
2018-03-29 1:04 ` xiaolei li
2018-03-28 12:06 ` [PATCH 0/2] Fix some function description mismatches Richard Weinberger
2018-03-29 1:07 ` xiaolei li [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=1522285649.8261.5.camel@mhfsdcap03 \
--to=xiaolei.li-nus5lvnupcjwk0htik3j/w@public.gmane.org \
--cc=boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=richard-/L3Ra7n9ekc@public.gmane.org \
--cc=srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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