mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akira shimahara <akira215corp@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: rdunlap@infradead.org, zbr@ioremap.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/9] w1_therm: adding code comments and code reordering
Date: Fri, 15 May 2020 20:20:12 +0200	[thread overview]
Message-ID: <cc8dfc3e9b33951d43fbd6fb8d4bac0d07b3d2d5.camel@gmail.com> (raw)
In-Reply-To: <20200515142926.GA2438037@kroah.com>

Le vendredi 15 mai 2020 à 16:29 +0200, Greg KH a écrit :
> On Mon, May 11, 2020 at 10:35:35PM +0200, Akira Shimahara wrote:
> > Adding code comments to split code in dedicated parts. After the global
> > declarations (defines, macros and function declarations), code is organized
> > as follow :
> >  - Device and family dependent structures and functions
> >  - Interfaces functions
> >  - Helpers functions
> >  - Hardware functions
> >  - Sysfs interface functions
> > 
> > Signed-off-by: Akira Shimahara <akira215corp@gmail.com>
> > ---
> > Main motivation on the first patch of this serie is to clean up the code,
> > document it and reorder it to prepare the next patches, which are clearer
> > after this.
> > 
> > One main point is to keep all device/family dependent code gather at the
> > beginning to ease adding new devices if required.
> 
> Thanks for sticking with this.  Nice work, all now queued up.
> 
> greg k-h

Hi, 

I also would like to thanks you all for your time and your involvment to help
these patch to be pushed up.

Akira Shimahara


      reply	other threads:[~2020-05-15 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 20:35 Akira Shimahara
2020-05-15 14:29 ` Greg KH
2020-05-15 18:20   ` Akira shimahara [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=cc8dfc3e9b33951d43fbd6fb8d4bac0d07b3d2d5.camel@gmail.com \
    --to=akira215corp@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=zbr@ioremap.net \
    /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

Powered by JetHome