On Thu, 05 Nov 2020, Michał Mirosław wrote:
> On Thu, Nov 05, 2020 at 12:50:27PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the mfd tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > drivers/gpio/gpio-tps65910.c: In function
On Thu, Nov 05, 2020 at 12:50:27PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mfd tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpio/gpio-tps65910.c: In function 'tps65910_gpio_get':
> drivers/gpio/gpio-tps65910.c:31:2: error:
Hi all,
After merging the mfd tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/gpio/gpio-tps65910.c: In function 'tps65910_gpio_get':
drivers/gpio/gpio-tps65910.c:31:2: error: implicit declaration of function
'tps65910_reg_read'
On Fri, 17 Jul 2020, Stephen Rothwell wrote:
> Hi Lee,
>
> On Fri, 17 Jul 2020 07:56:36 +0100 Lee Jones wrote:
> >
> > > +static const char *kempld_devs[] = {
> >
> > Do you mind if I change this to 'kempld_dev_names' and still keep your
> > SoB?
>
> No worries, I just did a quick hack, so
Hi Lee,
On Fri, 17 Jul 2020 07:56:36 +0100 Lee Jones wrote:
>
> > +static const char *kempld_devs[] = {
>
> Do you mind if I change this to 'kempld_dev_names' and still keep your
> SoB?
No worries, I just did a quick hack, so if you neaten it up that would
be good.
--
Cheers,
Stephen
On Fri, 17 Jul 2020, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/mfd/kempld-core.c: In function 'kempld_register_cells_generic':
> drivers/mfd/kempld-core.c:105:13: error: assignment of
Hi all,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mfd/kempld-core.c: In function 'kempld_register_cells_generic':
drivers/mfd/kempld-core.c:105:13: error: assignment of read-only location
'devs[i++]'
105 | devs[i++] =
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mfd/cros_ec_dev.c: In function 'ec_device_probe':
drivers/mfd/cros_ec_dev.c:422:33: error: 'EC_FEATURE_FINGERPRINT' undeclared
(first use in this function); did you mean
Hi all,
After merging the mfd tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/mfd/tps65218.c: In function 'tps65218_probe':
drivers/mfd/tps65218.c:247:3: error: label 'err_irq' used but not defined
goto err_irq;
^~~~
Caused by commit
05ba643fa2ce
Hi Lee,
On Tue, 12 Dec 2017 08:13:10 + Lee Jones wrote:
>
> Yes, it's in:
>
> next-20171212 as 51bd7125f740
>
> Also, the pull request for it went out over a week ago:
>
> https://lkml.org/lkml/2017/12/4/142
>
> What's missing? Do you still see an issue with
Hi Lee,
On Tue, 12 Dec 2017 08:13:10 + Lee Jones wrote:
>
> Yes, it's in:
>
> next-20171212 as 51bd7125f740
>
> Also, the pull request for it went out over a week ago:
>
> https://lkml.org/lkml/2017/12/4/142
>
> What's missing? Do you still see an issue with the build?
Sorry about
On Tue, 12 Dec 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> On Wed, 6 Dec 2017 08:58:03 + Lee Jones wrote:
> >
> > On Wed, 06 Dec 2017, Stephen Rothwell wrote:
> >
> > > On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
> > >
> > > >
> > >
On Tue, 12 Dec 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> On Wed, 6 Dec 2017 08:58:03 + Lee Jones wrote:
> >
> > On Wed, 06 Dec 2017, Stephen Rothwell wrote:
> >
> > > On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
> > >
> > > >
> > > > > I added the following fix patch:
> > > >
Hi Lee,
On Wed, 6 Dec 2017 08:58:03 + Lee Jones wrote:
>
> On Wed, 06 Dec 2017, Stephen Rothwell wrote:
>
> > On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
> > >
> > > > I added the following fix patch:
> > > >
> > > > From: Stephen
Hi Lee,
On Wed, 6 Dec 2017 08:58:03 + Lee Jones wrote:
>
> On Wed, 06 Dec 2017, Stephen Rothwell wrote:
>
> > On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
> > >
> > > > I added the following fix patch:
> > > >
> > > > From: Stephen Rothwell
> > > > Date: Mon, 4 Dec 2017
On Wed, 06 Dec 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
> >
> > > I added the following fix patch:
> > >
> > > From: Stephen Rothwell
> > > Date: Mon, 4 Dec 2017 14:10:34 +1100
> > > Subject:
On Wed, 06 Dec 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
> >
> > > I added the following fix patch:
> > >
> > > From: Stephen Rothwell
> > > Date: Mon, 4 Dec 2017 14:10:34 +1100
> > > Subject: [PATCH] misc: rtsx: fix symbol clashes
> > >
>
Hi Lee,
On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
>
> > I added the following fix patch:
> >
> > From: Stephen Rothwell
> > Date: Mon, 4 Dec 2017 14:10:34 +1100
> > Subject: [PATCH] misc: rtsx: fix symbol clashes
> >
> > Signed-off-by:
Hi Lee,
On Mon, 4 Dec 2017 09:39:53 + Lee Jones wrote:
>
> > I added the following fix patch:
> >
> > From: Stephen Rothwell
> > Date: Mon, 4 Dec 2017 14:10:34 +1100
> > Subject: [PATCH] misc: rtsx: fix symbol clashes
> >
> > Signed-off-by: Stephen Rothwell
>
> Although I'm not sure
On Mon, 04 Dec 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3':
> (.text+0x5760): multiple definition of `.sd_power_off_card3v3'
>
On Mon, 04 Dec 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3':
> (.text+0x5760): multiple definition of `.sd_power_off_card3v3'
>
On Mon, Dec 04, 2017 at 02:19:56PM +1100, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3':
> (.text+0x5760): multiple definition of
On Mon, Dec 04, 2017 at 02:19:56PM +1100, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3':
> (.text+0x5760): multiple definition of
Hi Lee,
After merging the mfd tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3':
(.text+0x5760): multiple definition of `.sd_power_off_card3v3'
drivers/misc/cardreader/rtsx_pcr.o:(.text+0x4630): first defined
Hi Lee,
After merging the mfd tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3':
(.text+0x5760): multiple definition of `.sd_power_off_card3v3'
drivers/misc/cardreader/rtsx_pcr.o:(.text+0x4630): first defined
Hi Lee,
On Wed, 31 May 2017 12:23:32 +1000 Stephen Rothwell
wrote:
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
> obe':
>
Hi Lee,
On Wed, 31 May 2017 12:23:32 +1000 Stephen Rothwell
wrote:
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
> obe':
> drivers/usb/typec/typec_wcove.c:306:32: error:
Hi Darren,
On Wed, 31 May 2017 12:23:32 +1000 Stephen Rothwell
wrote:
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
> obe':
>
Hi Darren,
On Wed, 31 May 2017 12:23:32 +1000 Stephen Rothwell
wrote:
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
> obe':
> drivers/usb/typec/typec_wcove.c:306:32: error:
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
obe':
drivers/usb/typec/typec_wcove.c:306:32: error: 'struct intel_soc_pmic' has no
member named 'irq_chip_data_level2'
ret =
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
obe':
drivers/usb/typec/typec_wcove.c:306:32: error: 'struct intel_soc_pmic' has no
member named 'irq_chip_data_level2'
ret =
Hi Lee,
On Mon, 10 Apr 2017 07:55:52 +0100 Lee Jones wrote:
>
> I guess this is still causing an issue in -next?
Yeah.
> The patch has now been removed from mfd-next and the result pushed.
Thanks.
--
Cheers,
Stephen Rothwell
Hi Lee,
On Mon, 10 Apr 2017 07:55:52 +0100 Lee Jones wrote:
>
> I guess this is still causing an issue in -next?
Yeah.
> The patch has now been removed from mfd-next and the result pushed.
Thanks.
--
Cheers,
Stephen Rothwell
On Mon, 10 Apr 2017, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 04 Apr 2017 15:31:15 +0300 Andy Shevchenko
> wrote:
> >
> > On Tue, 2017-04-04 at 09:21 +0100, Lee Jones wrote:
> > > On Tue, 04 Apr 2017, Lee Jones wrote:
> > >
> > > > On Tue, 04 Apr
On Mon, 10 Apr 2017, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 04 Apr 2017 15:31:15 +0300 Andy Shevchenko
> wrote:
> >
> > On Tue, 2017-04-04 at 09:21 +0100, Lee Jones wrote:
> > > On Tue, 04 Apr 2017, Lee Jones wrote:
> > >
> > > > On Tue, 04 Apr 2017, Stephen Rothwell wrote:
> > > >
Hi all,
On Tue, 04 Apr 2017 15:31:15 +0300 Andy Shevchenko
wrote:
>
> On Tue, 2017-04-04 at 09:21 +0100, Lee Jones wrote:
> > On Tue, 04 Apr 2017, Lee Jones wrote:
> >
> > > On Tue, 04 Apr 2017, Stephen Rothwell wrote:
> > >
> > > > After merging the mfd
Hi all,
On Tue, 04 Apr 2017 15:31:15 +0300 Andy Shevchenko
wrote:
>
> On Tue, 2017-04-04 at 09:21 +0100, Lee Jones wrote:
> > On Tue, 04 Apr 2017, Lee Jones wrote:
> >
> > > On Tue, 04 Apr 2017, Stephen Rothwell wrote:
> > >
> > > > After merging the mfd tree, today's linux-next build
On Tue, 2017-04-04 at 09:21 +0100, Lee Jones wrote:
> On Tue, 04 Apr 2017, Lee Jones wrote:
>
> > On Tue, 04 Apr 2017, Stephen Rothwell wrote:
> >
> > > Hi Lee,
> > >
> > > After merging the mfd tree, today's linux-next build (powerpc
> > > allyesconfig) failed like this:
> > >
> > >
On Tue, 2017-04-04 at 09:21 +0100, Lee Jones wrote:
> On Tue, 04 Apr 2017, Lee Jones wrote:
>
> > On Tue, 04 Apr 2017, Stephen Rothwell wrote:
> >
> > > Hi Lee,
> > >
> > > After merging the mfd tree, today's linux-next build (powerpc
> > > allyesconfig) failed like this:
> > >
> > >
On Tue, 04 Apr 2017, Lee Jones wrote:
> On Tue, 04 Apr 2017, Stephen Rothwell wrote:
>
> > Hi Lee,
> >
> > After merging the mfd tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > /home/sfr/next/next/drivers/mfd/intel_soc_pmic_bxtwc.c:25:31: fatal error:
> >
On Tue, 04 Apr 2017, Lee Jones wrote:
> On Tue, 04 Apr 2017, Stephen Rothwell wrote:
>
> > Hi Lee,
> >
> > After merging the mfd tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > /home/sfr/next/next/drivers/mfd/intel_soc_pmic_bxtwc.c:25:31: fatal error:
> >
On Tue, 04 Apr 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> /home/sfr/next/next/drivers/mfd/intel_soc_pmic_bxtwc.c:25:31: fatal error:
> asm/intel_pmc_ipc.h: No such file or directory
>
> Caused
On Tue, 04 Apr 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> /home/sfr/next/next/drivers/mfd/intel_soc_pmic_bxtwc.c:25:31: fatal error:
> asm/intel_pmc_ipc.h: No such file or directory
>
> Caused
Hi Lee,
After merging the mfd tree, today's linux-next build (powerpc
allyesconfig) failed like this:
/home/sfr/next/next/drivers/mfd/intel_soc_pmic_bxtwc.c:25:31: fatal error:
asm/intel_pmc_ipc.h: No such file or directory
Caused by commit
eb2a445f7d8f ("mfd: intel_soc_pmic: Fix a mess
Hi Lee,
After merging the mfd tree, today's linux-next build (powerpc
allyesconfig) failed like this:
/home/sfr/next/next/drivers/mfd/intel_soc_pmic_bxtwc.c:25:31: fatal error:
asm/intel_pmc_ipc.h: No such file or directory
Caused by commit
eb2a445f7d8f ("mfd: intel_soc_pmic: Fix a mess
On Tue, Mar 01, 2016 at 01:35:58AM +, Kuninori Morimoto wrote:
> I noticed that you reborned regmap_write_bits() on your latest tree.
> I think using/adding regmap_force_update_bits() is good idea IMO.
> Can I create such patch ?
It might make more sense to rename _force_update_bits() to
On Tue, Mar 01, 2016 at 01:35:58AM +, Kuninori Morimoto wrote:
> I noticed that you reborned regmap_write_bits() on your latest tree.
> I think using/adding regmap_force_update_bits() is good idea IMO.
> Can I create such patch ?
It might make more sense to rename _force_update_bits() to
Hi Mark
I noticed that you reborned regmap_write_bits() on your latest tree.
I think using/adding regmap_force_update_bits() is good idea IMO.
Can I create such patch ?
> Oops, it is my fault. Can you check/test this patch ?
>
>
> From: Kuninori Morimoto
Hi Mark
I noticed that you reborned regmap_write_bits() on your latest tree.
I think using/adding regmap_force_update_bits() is good idea IMO.
Can I create such patch ?
> Oops, it is my fault. Can you check/test this patch ?
>
>
> From: Kuninori Morimoto
> Date: Tue, 1 Mar
Hi Stephen, Lee
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/regulator/tps65086-regulator.c:194:9: error: implicit declaration of
> function 'regmap_write_bits' [-Werror=implicit-function-declaration]
>ret =
Hi Stephen, Lee
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/regulator/tps65086-regulator.c:194:9: error: implicit declaration of
> function 'regmap_write_bits' [-Werror=implicit-function-declaration]
>ret =
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/regulator/tps65086-regulator.c:194:9: error: implicit declaration of
function 'regmap_write_bits' [-Werror=implicit-function-declaration]
ret = regmap_write_bits(config->regmap,
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/regulator/tps65086-regulator.c:194:9: error: implicit declaration of
function 'regmap_write_bits' [-Werror=implicit-function-declaration]
ret = regmap_write_bits(config->regmap,
On Friday 16 October 2015 12:27:04 Stephen Rothwell wrote:
> Hi Arnd,
>
> On Thu, 15 Oct 2015 14:28:20 +0200 Arnd Bergmann wrote:
> >
> > diff --git a/include/asm-generic/io-64-nonatomic-hi-lo.h
> > b/include/asm-generic/io-64-nonatomic-hi-lo.h
> > new file mode 100644
> > index
On Friday 16 October 2015 12:27:04 Stephen Rothwell wrote:
> Hi Arnd,
>
> On Thu, 15 Oct 2015 14:28:20 +0200 Arnd Bergmann wrote:
> >
> > diff --git a/include/asm-generic/io-64-nonatomic-hi-lo.h
> > b/include/asm-generic/io-64-nonatomic-hi-lo.h
> > new file mode 100644
> > index
Hi Arnd,
On Thu, 15 Oct 2015 14:28:20 +0200 Arnd Bergmann wrote:
>
> diff --git a/include/asm-generic/io-64-nonatomic-hi-lo.h
> b/include/asm-generic/io-64-nonatomic-hi-lo.h
> new file mode 100644
> index ..32b73abce1b0
> --- /dev/null
> +++
On Thursday 15 October 2015 14:04:07 Christoph Hellwig wrote:
> On Thu, Oct 15, 2015 at 10:59:32AM +0200, Arnd Bergmann wrote:
> > The patch looks good, should we do something to prevent that from
> > becoming a problem when Linus pulls our branches?
> >
> > This commit is at the bottom of my
On Thu, Oct 15, 2015 at 10:59:32AM +0200, Arnd Bergmann wrote:
> The patch looks good, should we do something to prevent that from
> becoming a problem when Linus pulls our branches?
>
> This commit is at the bottom of my asm-generic git tree, so Lee could merge
> that one commit into his tree
On Thu, 2015-10-15 at 10:59 +0200, Arnd Bergmann wrote:
> >
> On Thursday 15 October 2015 13:26:02 Stephen Rothwell wrote:
> However, I also now see that
> drivers/net/ethernet/hisilicon/hns/hns_dsaf_xgmac.c
> has the same problem, so maybe it's better to add a temporary file
> with the old
On Thu, 15 Oct 2015, Arnd Bergmann wrote:
> On Thursday 15 October 2015 13:26:02 Stephen Rothwell wrote:
> > After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > drivers/mfd/intel-lpss.c:29:47: fatal error:
> >
On Thursday 15 October 2015 13:26:02 Stephen Rothwell wrote:
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/mfd/intel-lpss.c:29:47: fatal error:
> asm-generic/io-64-nonatomic-lo-hi.h: No such file or directory
> #include
>
On Thu, Oct 15, 2015 at 10:59:32AM +0200, Arnd Bergmann wrote:
> The patch looks good, should we do something to prevent that from
> becoming a problem when Linus pulls our branches?
>
> This commit is at the bottom of my asm-generic git tree, so Lee could merge
> that one commit into his tree
On Thursday 15 October 2015 14:04:07 Christoph Hellwig wrote:
> On Thu, Oct 15, 2015 at 10:59:32AM +0200, Arnd Bergmann wrote:
> > The patch looks good, should we do something to prevent that from
> > becoming a problem when Linus pulls our branches?
> >
> > This commit is at the bottom of my
On Thu, 15 Oct 2015, Arnd Bergmann wrote:
> On Thursday 15 October 2015 13:26:02 Stephen Rothwell wrote:
> > After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > drivers/mfd/intel-lpss.c:29:47: fatal error:
> >
On Thursday 15 October 2015 13:26:02 Stephen Rothwell wrote:
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/mfd/intel-lpss.c:29:47: fatal error:
> asm-generic/io-64-nonatomic-lo-hi.h: No such file or directory
> #include
>
On Thu, 2015-10-15 at 10:59 +0200, Arnd Bergmann wrote:
> >
> On Thursday 15 October 2015 13:26:02 Stephen Rothwell wrote:
> However, I also now see that
> drivers/net/ethernet/hisilicon/hns/hns_dsaf_xgmac.c
> has the same problem, so maybe it's better to add a temporary file
> with the old
Hi Arnd,
On Thu, 15 Oct 2015 14:28:20 +0200 Arnd Bergmann wrote:
>
> diff --git a/include/asm-generic/io-64-nonatomic-hi-lo.h
> b/include/asm-generic/io-64-nonatomic-hi-lo.h
> new file mode 100644
> index ..32b73abce1b0
> --- /dev/null
> +++
Hi Stephen,
[auto build test ERROR on next-20151013 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Stephen-Rothwell/linux-next-build-failure-after-merge-of-the-mfd-tree/20151015-102814
config: i386
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mfd/intel-lpss.c:29:47: fatal error:
asm-generic/io-64-nonatomic-lo-hi.h: No such file or directory
#include
^
Caused by commit
Hi Stephen,
[auto build test ERROR on next-20151013 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Stephen-Rothwell/linux-next-build-failure-after-merge-of-the-mfd-tree/20151015-102814
config: i386
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mfd/intel-lpss.c:29:47: fatal error:
asm-generic/io-64-nonatomic-lo-hi.h: No such file or directory
#include
^
Caused by commit
Hi Stephen,
On Wed, Mar 04, 2015 at 11:34:29AM +1100, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/mfd/mt6397-core.c: In function 'mt6397_irq_domain_map':
> drivers/mfd/mt6397-core.c:124:2:
Hi all,
On Wed, 4 Mar 2015 11:34:29 +1100 Stephen Rothwell
wrote:
>
> After merging the mfd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
My email to Flora Fu bounced:
: host mailgw02.mediatek.com[210.61.82.184] said: 550
Relaying mail to flora...@mediatek.com
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/mfd/mt6397-core.c: In function 'mt6397_irq_domain_map':
drivers/mfd/mt6397-core.c:124:2: error: implicit declaration of function
'set_irq_flags' [-Werror=implicit-function-declaration]
Hi Stephen,
On Wed, Mar 04, 2015 at 11:34:29AM +1100, Stephen Rothwell wrote:
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/mfd/mt6397-core.c: In function 'mt6397_irq_domain_map':
drivers/mfd/mt6397-core.c:124:2: error:
Hi all,
On Wed, 4 Mar 2015 11:34:29 +1100 Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
My email to Flora Fu flora...@mediatek.com bounced:
flora...@mediatek.com: host
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/mfd/mt6397-core.c: In function 'mt6397_irq_domain_map':
drivers/mfd/mt6397-core.c:124:2: error: implicit declaration of function
'set_irq_flags' [-Werror=implicit-function-declaration]
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/mfd/sky81452.c:29:0:
include/linux/mfd/sky81452.h:24:52: fatal error:
linux/platform_data/sky81452-backlight.h: No such file or directory
#include
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/mfd/sky81452.c:29:0:
include/linux/mfd/sky81452.h:24:52: fatal error:
linux/platform_data/sky81452-backlight.h: No such file or directory
#include
On Tue, 04 Nov 2014, Krzysztof Kozlowski wrote:
> On wto, 2014-11-04 at 16:40 +1100, Stephen Rothwell wrote:
> >
> > After merging the mfd tree, today's linux-next build (powerpc allyesconfig)
> > failed like this:
[Crash, bang, wallop]
> > And so on ...
> >
> > Caused by commit 9d5f4c2c748e
On Tue, 04 Nov 2014, Krzysztof Kozlowski wrote:
On wto, 2014-11-04 at 16:40 +1100, Stephen Rothwell wrote:
After merging the mfd tree, today's linux-next build (powerpc allyesconfig)
failed like this:
[Crash, bang, wallop]
And so on ...
Caused by commit 9d5f4c2c748e (mfd:
On wto, 2014-11-04 at 16:40 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mfd tree, today's linux-next build (powerpc allyesconfig)
> failed like this:
>
> drivers/regulator/max77686.c:432:13: warning: 'struct max77686_platform_data'
> declared inside parameter list
>
Hi all,
After merging the mfd tree, today's linux-next build (powerpc allyesconfig)
failed like this:
drivers/regulator/max77686.c:432:13: warning: 'struct max77686_platform_data'
declared inside parameter list
struct max77686_platform_data *pdata)
^
Hi all,
After merging the mfd tree, today's linux-next build (powerpc allyesconfig)
failed like this:
drivers/regulator/max77686.c:432:13: warning: 'struct max77686_platform_data'
declared inside parameter list
struct max77686_platform_data *pdata)
^
On wto, 2014-11-04 at 16:40 +1100, Stephen Rothwell wrote:
Hi all,
After merging the mfd tree, today's linux-next build (powerpc allyesconfig)
failed like this:
drivers/regulator/max77686.c:432:13: warning: 'struct max77686_platform_data'
declared inside parameter list
struct
On Sat, 23 Aug 2014, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: "wm8994_base_regmap_config" [drivers/mfd/wm8994-core.ko] undefined!
> ERROR: "wm8994_irq_init" [drivers/mfd/wm8994-core.ko]
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: "wm8994_base_regmap_config" [drivers/mfd/wm8994-core.ko] undefined!
ERROR: "wm8994_irq_init" [drivers/mfd/wm8994-core.ko] undefined!
ERROR: "wm1811_regmap_config"
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: wm8994_base_regmap_config [drivers/mfd/wm8994-core.ko] undefined!
ERROR: wm8994_irq_init [drivers/mfd/wm8994-core.ko] undefined!
ERROR: wm1811_regmap_config [drivers/mfd/wm8994-core.ko]
On Sat, 23 Aug 2014, Stephen Rothwell wrote:
Hi Lee,
After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: wm8994_base_regmap_config [drivers/mfd/wm8994-core.ko] undefined!
ERROR: wm8994_irq_init [drivers/mfd/wm8994-core.ko] undefined!
Hi Rob,
On Tue, Apr 09, 2013 at 11:50:30AM -0500, Rob Herring wrote:
> On Tue, Apr 9, 2013 at 11:12 AM, Samuel Ortiz wrote:
> >
> > On Tue, Apr 09, 2013 at 07:47:40PM +0400, Alexander Shiyan wrote:
> >> > On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
>
> [...]
>
> >> From
On Tue, Apr 9, 2013 at 11:12 AM, Samuel Ortiz wrote:
> Hi Alexander,
>
> On Tue, Apr 09, 2013 at 07:47:40PM +0400, Alexander Shiyan wrote:
>> > On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
[...]
>> From 3296415f29818a430bad12c92dc65cd81e4d133f Mon Sep 17 00:00:00 2001
>>
Hi Alexander,
On Tue, Apr 09, 2013 at 07:47:40PM +0400, Alexander Shiyan wrote:
> > On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
> > > > > > After merging the mfd tree, today's linux-next build (x86_64
> > > > > > allmodconfig)
> > > > > > failed like this:
> > > > > >
> >
> On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
> > > > > After merging the mfd tree, today's linux-next build (x86_64
> > > > > allmodconfig)
> > > > > failed like this:
> > > > >
> > > > > drivers/regulator/anatop-regulator.c: In function
> > > > >
Hi Alexander,
On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
> > > > After merging the mfd tree, today's linux-next build (x86_64
> > > > allmodconfig)
> > > > failed like this:
> > > >
> > > > drivers/regulator/anatop-regulator.c: In function
> > > >
Hi Alexander,
On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
drivers/regulator/anatop-regulator.c: In function
'anatop_regulator_probe':
On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
drivers/regulator/anatop-regulator.c: In function
'anatop_regulator_probe':
Hi Alexander,
On Tue, Apr 09, 2013 at 07:47:40PM +0400, Alexander Shiyan wrote:
On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
After merging the mfd tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
On Tue, Apr 9, 2013 at 11:12 AM, Samuel Ortiz sa...@linux.intel.com wrote:
Hi Alexander,
On Tue, Apr 09, 2013 at 07:47:40PM +0400, Alexander Shiyan wrote:
On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
[...]
From 3296415f29818a430bad12c92dc65cd81e4d133f Mon Sep 17
Hi Rob,
On Tue, Apr 09, 2013 at 11:50:30AM -0500, Rob Herring wrote:
On Tue, Apr 9, 2013 at 11:12 AM, Samuel Ortiz sa...@linux.intel.com wrote:
On Tue, Apr 09, 2013 at 07:47:40PM +0400, Alexander Shiyan wrote:
On Mon, Apr 08, 2013 at 08:27:49PM +0400, Alexander Shiyan wrote:
[...]
> > > After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> > > failed like this:
> > >
> > > drivers/regulator/anatop-regulator.c: In function
> > > 'anatop_regulator_probe':
> > > drivers/regulator/anatop-regulator.c:134:2: error: implicit declaration
> > > of function
1 - 100 of 119 matches
Mail list logo