linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Twiss <stwiss.opensource@diasemi.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 00/22] mfd: demodularization of non-modular drivers
Date: Wed, 7 Aug 2019 10:43:02 +0000	[thread overview]
Message-ID: <VI1PR10MB219250E43C2C31F73387DCF5FED40@VI1PR10MB2192.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20181207203021.GR23156@windriver.com>

Hi Paul,

I will not be able to make these changes to support modularity any more.

Although the support.opensource@diasemi.com e-mail address for Support
is still working, I will not be able to review your patches if you were to re-send
them again.

Regards,
Stephen

On 07 December 2018 20:30, Paul Gortmaker 
> > On 03 December 2018 04:23, Paul Gortmaker wrote:
> > > Subject: [PATCH v2 00/22] mfd: demodularization of non-modular drivers
> > >
> > > [v1 --> v2: add some more commits as requested by Lee (MFD maintainer),
> > >  update the 00/NN text; re-do build and link testing on new linux-next. ]
> > >
> > > This group of MFD drivers are all controlled by "bool" Kconfig settings,
> > > but contain various amounts of largely pointless uses of infrastructure
> > > related to modular operations, even though they can't be built modular.
> > >
> > > We can easily remove/replace all of it.  We are trying to make driver
> > > code consistent with the Makefiles/Kconfigs that control them.
> >
> > For the DA9052 and DA9055, changes:
> >
> > -  drivers/mfd/da9052-core.c         | 11 -----------
> > -  drivers/mfd/da9052-i2c.c          | 22 ++-------------------
> > -  drivers/mfd/da9052-irq.c          |  1 -
> > -  drivers/mfd/da9052-spi.c          | 22 ++-------------------
> > -  drivers/mfd/da9055-core.c         | 13 ++-----------
> > -  drivers/mfd/da9055-i2c.c          | 24 ++---------------------
> >
> > The responsibility can fall back to Dialog for these changes. We will
> > submit Kconfig patches for these and make them explicitly non-modular.
> > This will remove the ambiguity caused by the Kconfig bool options.
> 
> Just FYI, I dropped the diasemi commits from my v3 send.
> 
> https://lore.kernel.org/lkml/1544213465-16259-1-git-send-email-
> paul.gortmaker@windriver.com/
> 
> Thanks for taking on the modular conversions.



      parent reply	other threads:[~2019-08-07 10:43 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  4:23 [PATCH v2 00/22] mfd: demodularization of non-modular drivers Paul Gortmaker
2018-12-03  4:23 ` [PATCH 01/22] mfd: aat2870-core: Make it explicitly non-modular Paul Gortmaker
2018-12-03  4:23 ` [PATCH 02/22] mfd: adp5520: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 03/22] mfd: as3711: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 04/22] mfd: da903x: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 05/22] mfd: da9052-*: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 06/22] mfd: da9055-i2c: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 07/22] mfd: da9055-core: make " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 08/22] mfd: db8500-prcmu: drop unused MODULE_ tags from non-modular code Paul Gortmaker
2018-12-07 12:25   ` Linus Walleij
2018-12-03  4:23 ` [PATCH 09/22] mfd: htc-i2cpld: Make it explicitly non-modular Paul Gortmaker
2018-12-03  4:23 ` [PATCH 10/22] mfd: max8925-core: drop unused MODULE_ tags from non-modular code Paul Gortmaker
2018-12-03  4:23 ` [PATCH 11/22] mfd: rc5t583: Make it explicitly non-modular Paul Gortmaker
2018-12-03  4:23 ` [PATCH 12/22] mfd: sta2x11: drop unused MODULE_ tags from non-modular code Paul Gortmaker
2018-12-03 11:14   ` Lee Jones
2018-12-03 15:07     ` Paul Gortmaker
2018-12-04  9:23       ` Davide Ciminaghi
2018-12-07 16:39     ` Alessandro Rubini
2018-12-03  4:23 ` [PATCH 13/22] mfd: syscon: Make it explicitly non-modular Paul Gortmaker
2018-12-03  4:23 ` [PATCH 14/22] mfd: tps65090: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 15/22] mfd: tps65910: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 16/22] mfd: tps80031: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 17/22] mfd: wm831x-spi: " Paul Gortmaker
2018-12-03  4:23 ` [PATCH 18/22] mfd: wm831x-i2c: " Paul Gortmaker
2018-12-05 11:38   ` Charles Keepax
2018-12-07 18:16     ` Paul Gortmaker
2018-12-03  4:23 ` [PATCH 19/22] mfd: wm831x-core: drop unused MODULE_ tags from non-modular code Paul Gortmaker
2018-12-05 11:36   ` Charles Keepax
2018-12-03  4:23 ` [PATCH 20/22] mfd: wm8350-i2c: Make it explicitly non-modular Paul Gortmaker
2018-12-05 11:39   ` Charles Keepax
2018-12-03  4:23 ` [PATCH 21/22] mfd: wm8350-core: drop unused MODULE_ tags from non-modular code Paul Gortmaker
2018-12-05 11:39   ` Charles Keepax
2018-12-03  4:23 ` [PATCH 22/22] mfd: wm8400-core: Make it explicitly non-modular Paul Gortmaker
2018-12-05 11:41   ` Charles Keepax
2018-12-05 11:35 ` [PATCH v2 00/22] mfd: demodularization of non-modular drivers Charles Keepax
2018-12-05 11:48   ` Linus Walleij
2018-12-05 13:40     ` Charles Keepax
2018-12-05 11:50 ` Linus Walleij
2018-12-05 12:01 ` Steve Twiss
2018-12-05 12:12   ` Steve Twiss
2018-12-05 18:08   ` Paul Gortmaker
     [not found]   ` <20181207203021.GR23156@windriver.com>
2019-08-07 10:43     ` Steve Twiss [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=VI1PR10MB219250E43C2C31F73387DCF5FED40@VI1PR10MB2192.EURPRD10.PROD.OUTLOOK.COM \
    --to=stwiss.opensource@diasemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.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;
as well as URLs for NNTP newsgroup(s).