From: Chanwoo Choi <cw00.choi@samsung.com>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: myungjoo.ham@samsung.com, yongjun_wei@trendmicro.com.cn,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] extcon: remove duplicated include from extcon-gpio.c
Date: Thu, 11 Oct 2012 10:38:38 +0900 [thread overview]
Message-ID: <5076231E.5080808@samsung.com> (raw)
In-Reply-To: <CAPgLHd-rLYsjcSTJC-72aRnDQ=0oBMh-ESyCq+g=51VPd4bF1A@mail.gmail.com>
On 10/07/2012 10:26 PM, Wei Yongjun wrote:
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> Remove duplicated include.
>
> dpatch engine is used to auto generate this patch.
> (https://github.com/weiyj/dpatch)
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> ---
This patch was already applied from Sachin Kamat and
you can check previous patch on below extcon-for-next git tree:
- http://git.infradead.org/users/kmpark/linux-samsung/commit/e16bce4f25980a4f0b02b5297e87673800be5474
Thank you,
Chanwoo Choi
prev parent reply other threads:[~2012-10-11 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 13:26 [PATCH] extcon: remove duplicated include from extcon-gpio.c Wei Yongjun
2012-10-11 1:38 ` Chanwoo Choi [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=5076231E.5080808@samsung.com \
--to=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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