public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: linux-kernel@vger.kernel.org
Cc: chanwoo@kernel.org, myungjoo.ham@samsung.com
Subject: Re: [PATCH 0/3] extcon: Clean-up the description and indentation of functions
Date: Wed, 16 Aug 2017 09:29:21 +0900	[thread overview]
Message-ID: <599391E1.6040008@samsung.com> (raw)
In-Reply-To: <1500255025-6946-1-git-send-email-cw00.choi@samsung.com>

On 2017년 07월 17일 10:30, Chanwoo Choi wrote:
> These patches just clean-up code for extcon functions.
> 
> Firstly, patch2 modifies the description for functions/structures
> in order to improve the readability and guide the role of
> functions more well.
> 
> Second, the extcon header file defines the functions
> which used the mismatched indentation. So, patch3 fix them.
> 
> Lastly, patch1 just removes the unused definition.
> 
> Chanwoo Choi (3):
>   extcon: Remove unused CABLE_NAME_MAX definition
>   extcon: Correct description to improve the readability
>   extcon: Use tab instead of space for indentation
> 
>  drivers/extcon/devres.c |  50 +++++----
>  drivers/extcon/extcon.c | 275 +++++++++++++++++++++++-------------------------
>  include/linux/extcon.h  | 119 ++++++++++-----------
>  3 files changed, 212 insertions(+), 232 deletions(-)
> 

Applied these patches on extcon-next branch.

-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

      parent reply	other threads:[~2017-08-16  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170717013028epcas1p34be421b4d15aeb2dbb0a96f2ac27f8ec@epcas1p3.samsung.com>
2017-07-17  1:30 ` [PATCH 0/3] extcon: Clean-up the description and indentation of functions Chanwoo Choi
2017-07-17  1:30   ` [PATCH 1/3] extcon: Remove unused CABLE_NAME_MAX definition Chanwoo Choi
2017-07-17  1:30   ` [PATCH 2/3] extcon: Correct description to improve the readability Chanwoo Choi
2017-07-17  1:30   ` [PATCH 3/3] extcon: Use tab instead of space for indentation Chanwoo Choi
2017-08-16  0:29   ` 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=599391E1.6040008@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=chanwoo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.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