public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira shimahara <akira215corp@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: zbr@ioremap.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/9] w1_therm: creating w1_therm.h
Date: Wed, 06 May 2020 12:43:31 +0200	[thread overview]
Message-ID: <56b06ae0d110d650e65e4ed72fd44f870997893f.camel@gmail.com> (raw)
In-Reply-To: <20200506065134.GA2279499@kroah.com>

Le mercredi 06 mai 2020 à 08:51 +0200, Greg KH a écrit :
> > > Why is this function needed to be declared in this .h file?
> > > Why is any of this needed?  For some reason I thought you needed
> > > a .h
> > > file to make things simpler for other .c files, but if all of
> > > this is
> > > static, it's not needed at all, right?
> > > thanks,
> > > greg k-h
> > Hello,
> > Yes, you are right, header file could be avoided. But we separate
> > it
> > from .c for clarity purpose, and to ease future developpment (for
> > example adding support of new devices).
> > If you absolutely want to put everything in the .c file, I can do
> > it,
> > let me know.
> 
> 
> Keep it all in a .c file, only use .h files for when you need to
> share
> 
> it across multiple .c files, otherwise it's not needed.
> 
> 
> 
> thanks,
> 
> 
> 
> greg k-h

Hi, 

Ok well noted, I will do it tomorrow, and keep it as 8 patches.

Thanks for your time

Akira Shimahara


      reply	other threads:[~2020-05-06 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 22:59 [PATCH v4 1/9] w1_therm: creating w1_therm.h Akira Shimahara
2020-05-05 14:48 ` Greg KH
2020-05-05 21:04   ` Akira shimahara
2020-05-06  6:51     ` Greg KH
2020-05-06 10:43       ` 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=56b06ae0d110d650e65e4ed72fd44f870997893f.camel@gmail.com \
    --to=akira215corp@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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