mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/6] driver-core: platform: Provide helpers for multi-driver modules
Date: Fri, 25 Sep 2015 17:55:22 -0700	[thread overview]
Message-ID: <20150926005522.GA10987@kroah.com> (raw)
In-Reply-To: <20150925142944.GB22463@ulmo>

On Fri, Sep 25, 2015 at 04:29:44PM +0200, Thierry Reding wrote:
> On Thu, Sep 24, 2015 at 07:02:36PM +0200, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> > 
> > Some modules register several sub-drivers. Provide a helper that makes
> > it easy to register and unregister a list of sub-drivers, as well as
> > unwind properly on error.
> > 
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> >  Documentation/driver-model/platform.txt | 11 ++++++
> >  drivers/base/platform.c                 | 60 +++++++++++++++++++++++++++++++++
> >  include/linux/platform_device.h         |  5 +++
> >  3 files changed, 76 insertions(+)
> 
> Hi Greg,
> 
> In addition to patches 2-6 I have about two dozen patches across various
> subsystems that make use of this. I didn't want to spam everyone with
> all of them before you've given an indication about what you think about
> this patch.
> 
> The diffstat of the conversions I did is this:
> 
> 	drivers/crypto/n2_core.c                     | 17 +++++++----------
> 	drivers/edac/mpc85xx_edac.c                  | 16 ++++++++--------
> 	drivers/edac/mv64x60_edac.c                  | 39 +++++++++++----------------------------
> 	drivers/gpio/gpio-mpc5200.c                  | 17 +++++++----------
> 	drivers/gpu/drm/armada/armada_drv.c          | 16 +++++++---------
> 	drivers/gpu/drm/exynos/exynos_drm_drv.c      | 42 ++++++++----------------------------------
> 	drivers/gpu/drm/omapdrm/omap_drv.c           | 24 +++++++-----------------
> 	drivers/gpu/host1x/dev.c                     | 17 +++++++----------
> 	drivers/input/misc/sparcspkr.c               | 18 +++++++-----------
> 	drivers/iommu/msm_iommu_dev.c                | 25 +++++++------------------
> 	drivers/leds/leds-sunfire.c                  | 23 +++++++----------------
> 	drivers/mfd/sta2x11-mfd.c                    | 36 ++++++++++--------------------------
> 	drivers/net/ethernet/adi/bfin_mac.c          | 14 +++++++-------
> 	drivers/net/ethernet/broadcom/bcm63xx_enet.c | 28 ++++++++--------------------
> 	drivers/net/ethernet/freescale/fec_mpc52xx.c | 22 +++++++++-------------
> 	drivers/net/ethernet/marvell/mv643xx_eth.c   | 19 +++++++------------
> 	drivers/pinctrl/pinctrl-adi2.c               | 24 ++++++++----------------
> 	drivers/pinctrl/pinctrl-at91.c               | 14 +++++++-------
> 	drivers/regulator/lp8788-ldo.c               | 16 +++++++---------
> 	drivers/regulator/wm831x-dcdc.c              | 31 +++++++++----------------------
> 	drivers/regulator/wm831x-ldo.c               | 27 ++++++++-------------------
> 	drivers/tty/serial/mpsc.c                    | 19 ++++++++-----------
> 	drivers/usb/gadget/udc/dummy_hcd.c           | 17 ++++++++---------
> 	drivers/video/fbdev/s3c2410fb.c              | 15 +++++++--------
> 	24 files changed, 186 insertions(+), 350 deletions(-)
> 
> That's not too thrilling but in many cases this fixes a potential bug if
> a driver fails to register and the code doesn't properly unregister any
> previously registered drivers.
> 
> Anyway, if you think this is worth merging, how would you like to go
> about it? Do you want Acked-bys on all the patches and merge them
> through your tree? Perhaps the easiest would be to just merge this patch
> and then take the other patches through the maintainer trees after the
> core patch has landed?

The last thing is the easiest, but you have to wait a release cycle for
that.  Or I can take the whole series if you want to, just cc: the
proper subsystem maintainers when you send them.  It's up to you.

thanks,

greg k-h

  reply	other threads:[~2015-09-26  0:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 17:02 Thierry Reding
2015-09-24 17:02 ` [PATCH 2/6] drm/tegra: Use new multi-driver module helpers Thierry Reding
2015-09-24 17:02 ` [PATCH 3/6] drm/imx: Build monolithic driver Thierry Reding
2015-09-25  7:16   ` Philipp Zabel
2015-09-25 12:17     ` Thierry Reding
2015-09-25 13:09       ` Philipp Zabel
2015-09-25 13:13         ` Philipp Zabel
2015-09-25 14:21           ` Thierry Reding
2015-09-24 17:02 ` [PATCH 4/6] drm/imx: Do not export symbols Thierry Reding
2015-09-24 17:02 ` [PATCH 5/6] drm/sti: Build monolithic driver Thierry Reding
2015-10-05  8:22   ` Vincent ABRIOU
2015-09-24 17:02 ` [PATCH 6/6] drm/sti: Do not export symbols Thierry Reding
2015-10-05  8:22   ` Vincent ABRIOU
2015-09-25 10:27 ` [PATCH 1/6] driver-core: platform: Provide helpers for multi-driver modules Jani Nikula
2015-09-25 15:15   ` Thierry Reding
2015-09-28  6:37     ` Jani Nikula
2015-09-25 14:29 ` Thierry Reding
2015-09-26  0:55   ` Greg Kroah-Hartman [this message]
2015-09-25 15:23 ` Thierry Reding
2015-09-25 15:29 ` [PATCH v2] " Thierry Reding
2015-09-28  6:46   ` Andy Shevchenko
2015-09-28  9:05 ` [PATCH 1/6] " Daniel Vetter
2015-09-28 19:19   ` Eric Anholt

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=20150926005522.GA10987@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    /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