From: Alexander Alemayhu <alexander@alemayhu.com>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Anthony Sheldon <sheldon.anthony.sheldon@gmail.com>,
Karsten Keil <isdn@linux-pingi.de>,
Wei Yongjun <weiyongjun1@huawei.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] staging: i4l: pcbit: remove duplicated include from capi.c
Date: Tue, 18 Oct 2016 17:30:53 +0200 [thread overview]
Message-ID: <20161018153053.GA444@gmail.com> (raw)
In-Reply-To: <1476801430-25419-1-git-send-email-weiyj.lk@gmail.com>
On Tue, Oct 18, 2016 at 02:37:10PM +0000, Wei Yongjun wrote:
> From: Wei Yongjun <weiyongjun1@huawei.com>
>
> Remove duplicated include.
>
How did you discover that? Just curious if you used any tooling.
--
Mit freundlichen Grüßen
Alexander Alemayhu
next prev parent reply other threads:[~2016-10-18 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:37 [PATCH -next] staging: i4l: pcbit: remove duplicated include from capi.c Wei Yongjun
2016-10-18 15:30 ` Alexander Alemayhu [this message]
2016-10-18 15:45 ` Wei Yongjun
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=20161018153053.GA444@gmail.com \
--to=alexander@alemayhu.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sheldon.anthony.sheldon@gmail.com \
--cc=weiyj.lk@gmail.com \
--cc=weiyongjun1@huawei.com \
/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