From: Chanwoo Choi <cw00.choi@samsung.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
myungjoo.ham@samsung.com, linux-kernel@vger.kernel.org
Cc: linux-usb@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] extcon: max3355: kill unneeded #include's
Date: Mon, 21 Dec 2015 02:42:05 +0000 [thread overview]
Message-ID: <567766FD.2030004@samsung.com> (raw)
In-Reply-To: <6137530.8k1Rzov2Uy@wasted.cogentembedded.com>
On 2015년 12월 21일 03:31, Sergei Shtylyov wrote:
> Some #include's weren't needed from the start, some are left overs from the
> earlier driver versions... Kill 'em all! :-)
I don't prefer following expression. I think you should write the description
to maintain the formal style on the next.
- "... Kill 'em all! :-) "
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> ---
> The patch is against the 'extcon-next' branch of the 'extcon.git' repo.
> If possible, please fold this patch into the main MAX3355 driver patch.
>
> drivers/extcon/extcon-max3355.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> Index: extcon/drivers/extcon/extcon-max3355.c
> =================================> --- extcon.orig/drivers/extcon/extcon-max3355.c
> +++ extcon/drivers/extcon/extcon-max3355.c
> @@ -11,14 +11,9 @@
>
> #include <linux/extcon.h>
> #include <linux/gpio.h>
> -#include <linux/init.h>
> #include <linux/interrupt.h>
> -#include <linux/kernel.h>
> #include <linux/module.h>
> -#include <linux/of_gpio.h>
> #include <linux/platform_device.h>
> -#include <linux/slab.h>
> -#include <linux/workqueue.h>
>
> struct max3355_data {
> struct extcon_dev *edev;
>
I combine it on original patch.
Thanks,
Chanwoo Choi
WARNING: multiple messages have this Message-ID (diff)
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
myungjoo.ham@samsung.com, linux-kernel@vger.kernel.org
Cc: linux-usb@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] extcon: max3355: kill unneeded #include's
Date: Mon, 21 Dec 2015 11:42:05 +0900 [thread overview]
Message-ID: <567766FD.2030004@samsung.com> (raw)
In-Reply-To: <6137530.8k1Rzov2Uy@wasted.cogentembedded.com>
On 2015년 12월 21일 03:31, Sergei Shtylyov wrote:
> Some #include's weren't needed from the start, some are left overs from the
> earlier driver versions... Kill 'em all! :-)
I don't prefer following expression. I think you should write the description
to maintain the formal style on the next.
- "... Kill 'em all! :-) "
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> ---
> The patch is against the 'extcon-next' branch of the 'extcon.git' repo.
> If possible, please fold this patch into the main MAX3355 driver patch.
>
> drivers/extcon/extcon-max3355.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> Index: extcon/drivers/extcon/extcon-max3355.c
> ===================================================================
> --- extcon.orig/drivers/extcon/extcon-max3355.c
> +++ extcon/drivers/extcon/extcon-max3355.c
> @@ -11,14 +11,9 @@
>
> #include <linux/extcon.h>
> #include <linux/gpio.h>
> -#include <linux/init.h>
> #include <linux/interrupt.h>
> -#include <linux/kernel.h>
> #include <linux/module.h>
> -#include <linux/of_gpio.h>
> #include <linux/platform_device.h>
> -#include <linux/slab.h>
> -#include <linux/workqueue.h>
>
> struct max3355_data {
> struct extcon_dev *edev;
>
I combine it on original patch.
Thanks,
Chanwoo Choi
next prev parent reply other threads:[~2015-12-21 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 18:31 [PATCH] extcon: max3355: kill unneeded #include's Sergei Shtylyov
2015-12-20 18:31 ` Sergei Shtylyov
2015-12-21 2:42 ` Chanwoo Choi [this message]
2015-12-21 2:42 ` Chanwoo Choi
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=567766FD.2030004@samsung.com \
--to=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sergei.shtylyov@cogentembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.