mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Mark Brown <broonie@kernel.org>,
	Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Alexander Sverdlin <alexander.sverdlin@nsn.com>,
	Rob Herring <robherring2@gmail.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Matt Porter <matt.porter@linaro.org>,
	Koen Kooi <koen@dominion.thruhere.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alison Chaiken <Alison_Chaiken@mentor.com>,
	Dinh Nguyen <dinh.linux@gmail.com>, Jan Lubbe <jluebbe@lasnet.de>,
	Michael Stickel <ms@mycable.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Dirk Behme <dirk.behme@gmail.com>,
	Alan Tull <delicious.quinoa@gmail.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Michael Bohan <mbohan@codeaurora.org>,
	Ionut Nicu <ioan.nicu.ext@nsn.com>,
	Michal Simek <monstr@monstr.eu>,
	Matt Ranostay <mranostay@gmail.com>,
	Joel Becker <jlbec@evilplan.org>,
	devicetree@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
	linux-i2c@vger.kernel.org, linux-spi@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Pete Popov <pete.popov@konsulko.com>,
	Dan Malek <dan.malek@konsulko.com>,
	Georgi Vlaev <georgi.vlaev@konsulko.com>
Subject: Re: [PATCH] of: spi: Export single device registration method and\r accessors (v2)
Date: Fri, 21 Nov 2014 15:33:29 +0000	[thread overview]
Message-ID: <20141121153329.C4DDDC40D85@trevor.secretlab.ca> (raw)
In-Reply-To: <20141029122204.GG18557@sirena.org.uk>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2316 bytes --]

On Wed, 29 Oct 2014 12:22:04 +0000
, Mark Brown <broonie@kernel.org>
 wrote:
> On Wed, Oct 29, 2014 at 01:48:06PM +0200, Pantelis Antoniou wrote:
> > > On Oct 29, 2014, at 12:14 , Mark Brown <broonie@kernel.org> wrote:
> 
> > > This feels like there is an abstraction problem somewhere, whatever code
> > > is supposed to use this is going to need to be taught about each
> > > individual bus which is going to be tedious, I would expect that we'd
> > > have something like the bus being able to provide a callback which will
> > > get invoked whenever a new node appears on the parent node for the bus.
> 
> > There’s a whole patchset that does exactly this. 
> > Look at "OF: spi: Add OF notifier handler” and you’ll where this is used.
> 
> I deleted that unread I'm afraid; one of the reasons that you should use
> subject lines matching the styles for the subsystems is that it's one of
> the things people use to filter out things that actually need attention,
> if things are busy things that at first glance don't look terribly
> relevant (like changes to the OF core in this case) are likely to get
> looked at less urgently or just skipped.
> 
> A quick glance suggests that this is adding code inside the SPI core so
> it's still not explaining why anything is being exported, can you
> clarify please?

I have the same question. This doesn't look like it should be exporting
symbols.

Also, the way the patch is written causes a lot of code changes to get
interleaved in the diff. It would be better to split into two patches;
one that creates the new of_register_spi_device(), and a separate patch
to add the other new functions. It would be certainly easier to review
that way.

> 
> > > SubmittingPatches says.  Please also try to keep your CC list sane,
> > > CCing random people just means that you're increasing the volume of mail
> > > they have to process.  I'm surprised kernel.org accepts so many CCs.
> 
> > > I have to say I don't recall ever seeing v1...
> 
> > All of them are in the CC list for a reason. 
> 
> This is a single, standalone SPI patch - you didn't send it as part of a
> series (which is the only reason I read it).

Yes, this is part of the OF overlay series. It should have at least been
marked as [PATCH 7/8] and that it replaced the previous, buggy, patch 7.

g.


  reply	other threads:[~2014-11-21 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  8:40 Pantelis Antoniou
2014-10-29  9:08 ` Alexander Sverdlin
2014-10-29 10:14 ` Mark Brown
2014-10-29 11:48   ` Pantelis Antoniou
2014-10-29 12:22     ` Mark Brown
2014-11-21 15:33       ` Grant Likely [this message]
2014-11-21 15:44         ` Pantelis Antoniou
2014-11-21 16:53           ` Grant Likely

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=20141121153329.C4DDDC40D85@trevor.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=Alison_Chaiken@mentor.com \
    --cc=alexander.sverdlin@nsn.com \
    --cc=broonie@kernel.org \
    --cc=dan.malek@konsulko.com \
    --cc=delicious.quinoa@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinh.linux@gmail.com \
    --cc=dirk.behme@gmail.com \
    --cc=georgi.vlaev@konsulko.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ioan.nicu.ext@nsn.com \
    --cc=jlbec@evilplan.org \
    --cc=jluebbe@lasnet.de \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matt.porter@linaro.org \
    --cc=mbohan@codeaurora.org \
    --cc=monstr@monstr.eu \
    --cc=mranostay@gmail.com \
    --cc=ms@mycable.de \
    --cc=panto@antoniou-consulting.com \
    --cc=pete.popov@konsulko.com \
    --cc=robherring2@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=swarren@wwwdotorg.org \
    --cc=wsa@the-dreams.de \
    /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

all inboxes | Powered by JetHome®