Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758753AbaKUPdw (ORCPT ); Fri, 21 Nov 2014 10:33:52 -0500 Received: from mail-wi0-f178.google.com ([209.85.212.178]:41172 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758620AbaKUPdt (ORCPT ); Fri, 21 Nov 2014 10:33:49 -0500 From: Grant Likely Subject: Re: [PATCH] of: spi: Export single device registration method =?iso-8859-1?Q?and=0D?= accessors (v2) To: Mark Brown , Pantelis Antoniou Cc: Alexander Sverdlin , Rob Herring , Stephen Warren , Matt Porter , Koen Kooi , Greg Kroah-Hartman , Alison Chaiken , Dinh Nguyen , Jan Lubbe , Michael Stickel , Guenter Roeck , Dirk Behme , Alan Tull , Sascha Hauer , Michael Bohan , Ionut Nicu , Michal Simek , Matt Ranostay , Joel Becker , devicetree@vger.kernel.org, Wolfram Sang , linux-i2c@vger.kernel.org, linux-spi@vger.kernel.org, linux-kernel , Pete Popov , Dan Malek , Georgi Vlaev In-Reply-To: <20141029122204.GG18557@sirena.org.uk> References: <1414572037-11306-1-git-send-email-pantelis.antoniou@konsulko.com> <20141029101420.GT18557@sirena.org.uk> <6A3753C0-251A-4645-AD96-CB1D6521175F@antoniou-consulting.com> <20141029122204.GG18557@sirena.org.uk> Date: Fri, 21 Nov 2014 15:33:29 +0000 Message-Id: <20141121153329.C4DDDC40D85@trevor.secretlab.ca> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 29 Oct 2014 12:22:04 +0000 , Mark Brown wrote: > On Wed, Oct 29, 2014 at 01:48:06PM +0200, Pantelis Antoniou wrote: > > > On Oct 29, 2014, at 12:14 , Mark Brown 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/