devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: Chris Coffey <cmc@babblebit.net>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Peter Rosin <peda@axentia.se>, Slawomir Stepien <sst@poczta.fm>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] iio: potentiometer: Add driver for Microchip MCP41xxx/42xxx
Date: Sun, 11 Nov 2018 14:36:45 +0000	[thread overview]
Message-ID: <20181111143645.4ca692f2@archlinux> (raw)
In-Reply-To: <20181107094808.GB25433@himanshu-Vostro-3559>

On Wed, 7 Nov 2018 15:18:08 +0530
Himanshu Jha <himanshujha199640@gmail.com> wrote:

> On Wed, Nov 07, 2018 at 09:05:50AM +0000, Chris Coffey wrote:
> > Thank you for the review. I have a question inline.
> > 
> > On Tue, Nov 06, 2018 at 09:18:06PM +0530, Himanshu Jha wrote:  
> > > On Tue, Nov 06, 2018 at 11:31:30AM +0000, Chris Coffey wrote:  
> > > > This patch adds driver support for the Microchip MCP41xxx/42xxx family
> > > > of digital potentiometers:
> > > > 
> > > > DEVICE      Wipers  Positions   Resistance (kOhm)
> > > > MCP41010    1       256         10
> > > > MCP41050    1       256         50
> > > > MCP41100    1       256         100
> > > > MCP42010    2       256         10
> > > > MCP42050    2       256         50
> > > > MCP42100    2       256         100
> > > > 
> > > > Datasheet: http://ww1.microchip.com/downloads/en/devicedoc/11195c.pdf
> > > > 
> > > > Signed-off-by: Chris Coffey <cmc@babblebit.net>
> > > > ---
> > > >  .../bindings/iio/potentiometer/mcp41010.txt        |  29 +++  
> > > 
> > > WARNING: DT binding docs and includes should be a separate patch. 
> > > See: Documentation/devicetree/bindings/submitting-patches.txt
> > > 
> > > Please run checkpatch.pl on this patch once.
> > >   
> > 
> > Oops. I ran checkpatch.pl on the individual files, but neglected to run
> > it on the patch file itself. I'll split the patch in v2.  
> 
> No problem.
> 
> It is better for DT maintainers, and they get less spam. It was recent
> effort by Rob IIRC,
> 
> "133712a2ec84 checkpatch: DT bindings should be a separate patch"
> 
> When you run on source file use `-f` flag and on patch just naked
> run is fine.
> 
> > checkpatch.pl also reports a warning about the MAINTAINERS file:
> > WARNING: added, moved or deleted file(s), does MAINTAINERS need
> > updating?
> > 
> > ... but looking through the tree, many IIO drivers don't have
> > corresponding entries in MAINTAINERS; is this one of those checkpatch
> > warnings that can be safely ignored? Or should all new drivers have a
> > corresponding entry in MAINTAINERS?  
> 
> It's upto you actually. 
> Not a necessity to be a maintainer.
> 
> But when you add your name to MAINTAINERS you would need to review the
> patches sent on the driver and maybe test it too.
> 
> And if you're not sure, then leave it as-is!
> 
> Without the entry in MAINTAINERS too, you can review/test patches
> sent on your driver(which is what I do ..)
> 
> Obligations! ;)

Yes, mostly MAINTAINERS entries are needed when it's not obvious
from the driver who should be looking at patches.  Often this is
when someone else had taken it over later, or you want all patches
to be cc'd to a list of relevant people (so company mailing lists
for example).  If people want to put themselves in MAINTAINERS
then we never mind, but personally I don't see why every single
driver needs to be listed.

Jonathan

> 

  reply	other threads:[~2018-11-11 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 11:31 [PATCH] iio: potentiometer: Add driver for Microchip MCP41xxx/42xxx Chris Coffey
2018-11-06 15:48 ` Himanshu Jha
2018-11-07  9:05   ` Chris Coffey
2018-11-07  9:48     ` Himanshu Jha
2018-11-11 14:36       ` Jonathan Cameron [this message]
2018-11-06 16:37 ` Peter Rosin
2018-11-06 20:08   ` Peter Rosin
2018-11-07  9:25     ` Chris Coffey
2018-11-07  9:18   ` Chris Coffey
2018-11-11 14:55   ` Jonathan Cameron
2018-11-11 16:49     ` Peter Rosin
2018-11-11 17:07       ` Jonathan Cameron

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=20181111143645.4ca692f2@archlinux \
    --to=jic23@kernel.org \
    --cc=cmc@babblebit.net \
    --cc=devicetree@vger.kernel.org \
    --cc=himanshujha199640@gmail.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peda@axentia.se \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=sst@poczta.fm \
    /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;
as well as URLs for NNTP newsgroup(s).