linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from drivers/scsi/lpfc/lpfc_debugfs.c:46: drivers/scsi/lpfc/lpfc_debugfs.c: In function 'lpfc_idiag_queacc_write': drivers/scsi/lpfc/lpfc_sli4.h:1083:14: error: inlining

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (sparc defconfig) failed like this: drivers/scsi/qlogicpti.c:1285:27: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .eh_host_reset_handler = qlogicpti_reset,

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (sparc defconfig) failed like this: drivers/scsi/qlogicpti.c:1285:27: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .eh_host_reset_handler = qlogicpti_reset,

Re: linux-next: build failure after merge of the scsi tree

On 02/12/2017 05:32 PM, Stephen Rothwell wrote: > Hi all, > > On Mon, 6 Feb 2017 16:04:51 +1100 Stephen Rothwell > wrote: >> >> After merging the scsi tree, today's linux-next build (powerpc >> ppc64_defconfig) failed like this: >> >> In file included from

Re: linux-next: build failure after merge of the scsi tree

On 02/12/2017 05:32 PM, Stephen Rothwell wrote: > Hi all, > > On Mon, 6 Feb 2017 16:04:51 +1100 Stephen Rothwell > wrote: >> >> After merging the scsi tree, today's linux-next build (powerpc >> ppc64_defconfig) failed like this: >> >> In file included from include/uapi/linux/stddef.h:1:0, >>

Re: linux-next: build failure after merge of the scsi tree

Hi all, On Mon, 6 Feb 2017 16:04:51 +1100 Stephen Rothwell wrote: > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/uapi/linux/stddef.h:1:0, > from

Re: linux-next: build failure after merge of the scsi tree

Hi all, On Mon, 6 Feb 2017 16:04:51 +1100 Stephen Rothwell wrote: > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/uapi/linux/stddef.h:1:0, > from include/linux/stddef.h:4, >

linux-next: build failure after merge of the scsi tree

Hi all, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/uapi/linux/stddef.h:1:0, from include/linux/stddef.h:4, from include/uapi/linux/posix_types.h:4, from

linux-next: build failure after merge of the scsi tree

Hi all, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/uapi/linux/stddef.h:1:0, from include/linux/stddef.h:4, from include/uapi/linux/posix_types.h:4, from

Re: linux-next: build failure after merge of the scsi tree

On Sat, 2016-12-24 at 12:46 +0100, Thomas Gleixner wrote: > On Sat, 24 Dec 2016, Stephen Rothwell wrote: > > On Thu, 22 Dec 2016 16:56:34 -0800 James Bottomley < > > james.bottom...@hansenpartnership.com> wrote: > > > > > > On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > > > > Hi

Re: linux-next: build failure after merge of the scsi tree

On Sat, 2016-12-24 at 12:46 +0100, Thomas Gleixner wrote: > On Sat, 24 Dec 2016, Stephen Rothwell wrote: > > On Thu, 22 Dec 2016 16:56:34 -0800 James Bottomley < > > james.bottom...@hansenpartnership.com> wrote: > > > > > > On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > > > > Hi

Re: linux-next: build failure after merge of the scsi tree

On Sat, 24 Dec 2016, Stephen Rothwell wrote: > On Thu, 22 Dec 2016 16:56:34 -0800 James Bottomley > wrote: > > > > On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > > > Hi James, > > > > > > After merging the scsi tree, today's linux-next build

Re: linux-next: build failure after merge of the scsi tree

On Sat, 24 Dec 2016, Stephen Rothwell wrote: > On Thu, 22 Dec 2016 16:56:34 -0800 James Bottomley > wrote: > > > > On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > > > Hi James, > > > > > > After merging the scsi tree, today's linux-next build (x86_64 > > > allmodconfig) failed like

Re: linux-next: build failure after merge of the scsi tree

Hi Ingo, On Sat, 24 Dec 2016 11:15:08 +0100 Ingo Molnar wrote: > > Yeah, we'll handle it - that's why the final chunk of changes were left to > after > -rc1, to not cause such merge conflicts upstream. Excellent, thanks. > For now I've excluded the relevant -tip side

Re: linux-next: build failure after merge of the scsi tree

Hi Ingo, On Sat, 24 Dec 2016 11:15:08 +0100 Ingo Molnar wrote: > > Yeah, we'll handle it - that's why the final chunk of changes were left to > after > -rc1, to not cause such merge conflicts upstream. Excellent, thanks. > For now I've excluded the relevant -tip side commits from the

Re: linux-next: build failure after merge of the scsi tree

* Stephen Rothwell wrote: > Hi All, > > On Thu, 22 Dec 2016 16:56:34 -0800 James Bottomley > wrote: > > > > On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > > > Hi James, > > > > > > After merging the scsi tree,

Re: linux-next: build failure after merge of the scsi tree

* Stephen Rothwell wrote: > Hi All, > > On Thu, 22 Dec 2016 16:56:34 -0800 James Bottomley > wrote: > > > > On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > > > Hi James, > > > > > > After merging the scsi tree, today's linux-next build (x86_64 > > > allmodconfig) failed like

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/scsi/qedi/qedi_main.c: In function 'qedi_init': > drivers/scsi/qedi/qedi_main.c:2073:2: error: implicit

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2016-12-23 at 11:45 +1100, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/scsi/qedi/qedi_main.c: In function 'qedi_init': > drivers/scsi/qedi/qedi_main.c:2073:2: error: implicit

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/scsi/qedi/qedi_main.c: In function 'qedi_init': drivers/scsi/qedi/qedi_main.c:2073:2: error: implicit declaration of function 'register_hotcpu_notifier'

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/scsi/qedi/qedi_main.c: In function 'qedi_init': drivers/scsi/qedi/qedi_main.c:2073:2: error: implicit declaration of function 'register_hotcpu_notifier'

Re: linux-next: build failure after merge of the scsi tree

Thanks Stephen. Please consider this patch as Ack-by: Sreekanth Reddy Thanks, Sreekanth On Fri, Nov 13, 2015 at 7:05 AM, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > In file included from

Re: linux-next: build failure after merge of the scsi tree

Thanks Stephen. Please consider this patch as Ack-by: Sreekanth Reddy Thanks, Sreekanth On Fri, Nov 13, 2015 at 7:05 AM, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > allyesconfig)

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from drivers/scsi/mpt3sas/mpt3sas_scsih.c:59:0: drivers/scsi/mpt3sas/mpt3sas_scsih.c: In function '_scsih_io_done': drivers/scsi/mpt3sas/mpt3sas_base.h:1414:1: error:

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from drivers/scsi/mpt3sas/mpt3sas_scsih.c:59:0: drivers/scsi/mpt3sas/mpt3sas_scsih.c: In function '_scsih_io_done': drivers/scsi/mpt3sas/mpt3sas_base.h:1414:1: error:

Re: linux-next: build failure after merge of the scsi tree

On Tue, 2015-06-02 at 18:06 +1000, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/usb/gadget/function/f_mass_storage.c:280:12: error: > 'MAX_COMMAND_SIZE' undeclared here (not in a function) >

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/usb/gadget/function/f_mass_storage.c:280:12: error: 'MAX_COMMAND_SIZE' undeclared here (not in a function) u8 cmnd[MAX_COMMAND_SIZE]; ^ Caused by commit 0e640c799103

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/usb/gadget/function/f_mass_storage.c:280:12: error: 'MAX_COMMAND_SIZE' undeclared here (not in a function) u8 cmnd[MAX_COMMAND_SIZE]; ^ Caused by commit 0e640c799103

Re: linux-next: build failure after merge of the scsi tree

On Tue, 2015-06-02 at 18:06 +1000, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/usb/gadget/function/f_mass_storage.c:280:12: error: 'MAX_COMMAND_SIZE' undeclared here (not in a function) u8

Re: linux-next: build failure after merge of the scsi tree

On Wed, 2015-02-04 at 17:29 +1100, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/scsi/scsi_logging.c: In function 'sdev_prefix_printk': > drivers/scsi/scsi_logging.c:119:6: error: void value

Re: linux-next: build failure after merge of the scsi tree

On Wed, 2015-02-04 at 17:29 +1100, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/scsi_logging.c: In function 'sdev_prefix_printk': drivers/scsi/scsi_logging.c:119:6: error: void value not

Re: linux-next: build failure after merge of the scsi tree

(adding Christoph Hellwig) On Wed, 2015-02-04 at 17:29 +1100, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/scsi/scsi_logging.c: In function 'sdev_prefix_printk': >

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/scsi_logging.c: In function 'sdev_prefix_printk': drivers/scsi/scsi_logging.c:119:6: error: void value not ignored as it ought to be ret = dev_printk(level, >sdev_gendev,

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/scsi_logging.c: In function 'sdev_prefix_printk': drivers/scsi/scsi_logging.c:119:6: error: void value not ignored as it ought to be ret = dev_printk(level,

Re: linux-next: build failure after merge of the scsi tree

(adding Christoph Hellwig) On Wed, 2015-02-04 at 17:29 +1100, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/scsi_logging.c: In function 'sdev_prefix_printk':

Re: linux-next: build failure after merge of the scsi tree

On Mon, Nov 10, 2014 at 07:50:16AM -0800, James Bottomley wrote: > So your idea is Fenguang first then linux-next. Exactly. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: linux-next: build failure after merge of the scsi tree

On Mon, 2014-11-10 at 16:48 +0100, Christoph Hellwig wrote: > On Mon, Nov 10, 2014 at 07:21:30AM -0800, James Bottomley wrote: > > so that's adding the 3.18-incoming trees? > > Not yet. Those are for the buildbolt to find any issues before pushing > it to the actual for-3.x branch. It's a trick

Re: linux-next: build failure after merge of the scsi tree

On Mon, Nov 10, 2014 at 07:21:30AM -0800, James Bottomley wrote: > so that's adding the 3.18-incoming trees? Not yet. Those are for the buildbolt to find any issues before pushing it to the actual for-3.x branch. It's a trick I picked up from the nfsd tree. -- To unsubscribe from this list:

Re: linux-next: build failure after merge of the scsi tree

On Mon, 2014-11-10 at 14:46 +0100, Christoph Hellwig wrote: > On Mon, Nov 10, 2014 at 06:27:13AM +, Anish Bhatt wrote: > > Fix for this was sent out on thursday itself, but does not seem to be > > applied yet : > > http://marc.info/?l=linux-scsi=141529629911520=2 > > And I pulled it from

Re: linux-next: build failure after merge of the scsi tree

On Mon, Nov 10, 2014 at 06:27:13AM +, Anish Bhatt wrote: > Fix for this was sent out on thursday itself, but does not seem to be applied > yet : > http://marc.info/?l=linux-scsi=141529629911520=2 And I pulled it from drivers-for-3.18 early on Thursday, but that didn't propagate to James'

Re: linux-next: build failure after merge of the scsi tree

On Mon, Nov 10, 2014 at 06:27:13AM +, Anish Bhatt wrote: Fix for this was sent out on thursday itself, but does not seem to be applied yet : http://marc.info/?l=linux-scsim=141529629911520w=2 And I pulled it from drivers-for-3.18 early on Thursday, but that didn't propagate to James' tree

Re: linux-next: build failure after merge of the scsi tree

On Mon, 2014-11-10 at 14:46 +0100, Christoph Hellwig wrote: On Mon, Nov 10, 2014 at 06:27:13AM +, Anish Bhatt wrote: Fix for this was sent out on thursday itself, but does not seem to be applied yet : http://marc.info/?l=linux-scsim=141529629911520w=2 And I pulled it from

Re: linux-next: build failure after merge of the scsi tree

On Mon, Nov 10, 2014 at 07:21:30AM -0800, James Bottomley wrote: so that's adding the 3.18-incoming trees? Not yet. Those are for the buildbolt to find any issues before pushing it to the actual for-3.x branch. It's a trick I picked up from the nfsd tree. -- To unsubscribe from this list: send

Re: linux-next: build failure after merge of the scsi tree

On Mon, 2014-11-10 at 16:48 +0100, Christoph Hellwig wrote: On Mon, Nov 10, 2014 at 07:21:30AM -0800, James Bottomley wrote: so that's adding the 3.18-incoming trees? Not yet. Those are for the buildbolt to find any issues before pushing it to the actual for-3.x branch. It's a trick I

Re: linux-next: build failure after merge of the scsi tree

On Mon, Nov 10, 2014 at 07:50:16AM -0800, James Bottomley wrote: So your idea is Fenguang first then linux-next. Exactly. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at

RE: linux-next: build failure after merge of the scsi tree

...@vger.kernel.org; linux-kernel@vger.kernel.org; Anish Bhatt; Christoph Hellwig; Karen Xie Subject: linux-next: build failure after merge of the scsi tree Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/cxgbi/cxgb4i/cxgb4i.c

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/cxgbi/cxgb4i/cxgb4i.c: In function 'do_abort_req_rss': drivers/scsi/cxgbi/cxgb4i/cxgb4i.c:942:3: error: too many arguments to function 'send_tx_flowc_wr'

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/cxgbi/cxgb4i/cxgb4i.c: In function 'do_abort_req_rss': drivers/scsi/cxgbi/cxgb4i/cxgb4i.c:942:3: error: too many arguments to function 'send_tx_flowc_wr'

RE: linux-next: build failure after merge of the scsi tree

...@vger.kernel.org; linux-kernel@vger.kernel.org; Anish Bhatt; Christoph Hellwig; Karen Xie Subject: linux-next: build failure after merge of the scsi tree Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/cxgbi/cxgb4i

Re: linux-next: build failure after merge of the scsi tree

Hi Hannes, On Tue, 04 Nov 2014 08:07:51 +0100 Hannes Reinecke wrote: > > On 11/04/2014 05:43 AM, Stephen Rothwell wrote: > > > > After merging the scsi tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > In file included from include/linux/sched.h:17:0, from

Re: linux-next: build failure after merge of the scsi tree

Hi Hannes, On Tue, 04 Nov 2014 08:07:51 +0100 Hannes Reinecke h...@suse.de wrote: On 11/04/2014 05:43 AM, Stephen Rothwell wrote: After merging the scsi tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from include/linux/sched.h:17:0, from

Re: linux-next: build failure after merge of the scsi tree

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/04/2014 05:43 AM, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > In file included from include/linux/sched.h:17:0, from >

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from include/linux/sched.h:17:0, from include/linux/blkdev.h:4, from drivers/scsi/constants.c:10: drivers/scsi/constants.c: In function

Re: linux-next: build failure after merge of the scsi tree

Thanks, I've folded that patch into the one that caused the issue. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

Re: linux-next: build failure after merge of the scsi tree

Thanks, I've folded that patch into the one that caused the issue. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from include/linux/sched.h:17:0, from include/linux/blkdev.h:4, from drivers/scsi/constants.c:10: drivers/scsi/constants.c: In function

Re: linux-next: build failure after merge of the scsi tree

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/04/2014 05:43 AM, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (arm multi_v7_defconfig) failed like this: In file included from include/linux/sched.h:17:0, from include/linux/blkdev.h:4, from

Re: linux-next: build failure after merge of the scsi tree

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/2014 03:52 AM, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/scsi/scsi_lib.c: In function 'scsi_io_completion': >

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/scsi_lib.c: In function 'scsi_io_completion': drivers/scsi/scsi_lib.c:1048:5: error: implicit declaration of function 'SCSI_LOG_LEVEL' [-Werror=implicit-function-declaration]

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/scsi_lib.c: In function 'scsi_io_completion': drivers/scsi/scsi_lib.c:1048:5: error: implicit declaration of function 'SCSI_LOG_LEVEL' [-Werror=implicit-function-declaration]

Re: linux-next: build failure after merge of the scsi tree

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/2014 03:52 AM, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/scsi_lib.c: In function 'scsi_io_completion':

Re: linux-next: build failure after merge of the scsi tree

On 09/26/2014 04:57 AM, James Bottomley wrote: > On Fri, 2014-09-26 at 10:36 +0200, Christoph Hellwig wrote: >> On Fri, Sep 26, 2014 at 06:34:50PM +1000, Stephen Rothwell wrote: >>> Hi James, >>> >>> After merging the scsi tree, today's linux-next build (powerpc >>> ppc64_defconfig) failed like

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2014-09-26 at 10:36 +0200, Christoph Hellwig wrote: > On Fri, Sep 26, 2014 at 06:34:50PM +1000, Stephen Rothwell wrote: > > Hi James, > > > > After merging the scsi tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > drivers/scsi/ipr.c: In function

Re: linux-next: build failure after merge of the scsi tree

On Fri, Sep 26, 2014 at 06:34:50PM +1000, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/scsi/ipr.c: In function 'ipr_handle_log_data': > drivers/scsi/ipr.c:2468:15: error:

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/ipr.c: In function 'ipr_handle_log_data': drivers/scsi/ipr.c:2468:15: error: 'IPR_IOASC_HW_CMD_FAILED' undeclared (first use in this function) if (ioasc ==

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/ipr.c: In function 'ipr_handle_log_data': drivers/scsi/ipr.c:2468:15: error: 'IPR_IOASC_HW_CMD_FAILED' undeclared (first use in this function) if (ioasc ==

Re: linux-next: build failure after merge of the scsi tree

On Fri, Sep 26, 2014 at 06:34:50PM +1000, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/ipr.c: In function 'ipr_handle_log_data': drivers/scsi/ipr.c:2468:15: error: 'IPR_IOASC_HW_CMD_FAILED'

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2014-09-26 at 10:36 +0200, Christoph Hellwig wrote: On Fri, Sep 26, 2014 at 06:34:50PM +1000, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/ipr.c: In function

Re: linux-next: build failure after merge of the scsi tree

On 09/26/2014 04:57 AM, James Bottomley wrote: On Fri, 2014-09-26 at 10:36 +0200, Christoph Hellwig wrote: On Fri, Sep 26, 2014 at 06:34:50PM +1000, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this:

Re: linux-next: build failure after merge of the scsi tree

Quoting James Bottomley : On Fri, 2013-01-11 at 11:35 -0600, Brian King wrote: On 01/11/2013 10:05 AM, Greg KH wrote: > On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: >> On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: >>> It looks like this was a due to the fact that

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2013-01-11 at 11:35 -0600, Brian King wrote: > On 01/11/2013 10:05 AM, Greg KH wrote: > > On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: > >> On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: > >>> It looks like this was a due to the fact that the new patches > >>>

Re: linux-next: build failure after merge of the scsi tree

On 01/11/2013 10:05 AM, Greg KH wrote: > On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: >> On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: >>> It looks like this was a due to the fact that the new patches >>> added __devinit tags in the same merge window the __devinit tag

Re: linux-next: build failure after merge of the scsi tree

On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: > On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: > > It looks like this was a due to the fact that the new patches > > added __devinit tags in the same merge window the __devinit tag > > itself was getting removed. > > Not

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: > It looks like this was a due to the fact that the new patches > added __devinit tags in the same merge window the __devinit tag > itself was getting removed. Not exactly. The patch which makes them nops went into 3.8. Now there's a patch

Re: linux-next: build failure after merge of the scsi tree

It looks like this was a due to the fact that the new patches added __devinit tags in the same merge window the __devinit tag itself was getting removed. As to the sparse warnings, this patch fixed the ones that were actual bugs in the new code, although we could have made that more clear in the

Re: linux-next: build failure after merge of the scsi tree

It looks like this was a due to the fact that the new patches added __devinit tags in the same merge window the __devinit tag itself was getting removed. As to the sparse warnings, this patch fixed the ones that were actual bugs in the new code, although we could have made that more clear in the

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: It looks like this was a due to the fact that the new patches added __devinit tags in the same merge window the __devinit tag itself was getting removed. Not exactly. The patch which makes them nops went into 3.8. Now there's a patch

Re: linux-next: build failure after merge of the scsi tree

On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: It looks like this was a due to the fact that the new patches added __devinit tags in the same merge window the __devinit tag itself was getting removed. Not exactly.

Re: linux-next: build failure after merge of the scsi tree

On 01/11/2013 10:05 AM, Greg KH wrote: On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: It looks like this was a due to the fact that the new patches added __devinit tags in the same merge window the __devinit tag itself was

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2013-01-11 at 11:35 -0600, Brian King wrote: On 01/11/2013 10:05 AM, Greg KH wrote: On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: It looks like this was a due to the fact that the new patches added __devinit

Re: linux-next: build failure after merge of the scsi tree

Quoting James Bottomley james.bottom...@hansenpartnership.com: On Fri, 2013-01-11 at 11:35 -0600, Brian King wrote: On 01/11/2013 10:05 AM, Greg KH wrote: On Fri, Jan 11, 2013 at 03:37:17PM +, James Bottomley wrote: On Fri, 2013-01-11 at 09:27 -0600, Brian King wrote: It looks like

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2013-01-11 at 12:03 +1100, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/scsi/ipr.c:9138:22: error: expected '=', ',', ';', 'asm' or > '__attribute__' before 'ipr_enable_msix' >

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/ipr.c:9138:22: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ipr_enable_msix' drivers/scsi/ipr.c:9165:22: error: expected '=', ',', ';', 'asm' or

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/ipr.c:9138:22: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ipr_enable_msix' drivers/scsi/ipr.c:9165:22: error: expected '=', ',', ';', 'asm' or

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2013-01-11 at 12:03 +1100, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/scsi/ipr.c:9138:22: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ipr_enable_msix'

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2012-07-20 at 10:41 +1000, Stephen Rothwell wrote: > Hi James, > > After merging the scsi tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/base/dd.c:27:28: fatal error: scsi/scsi_scan.h: No such file or > directory > > Caused by commit

Re: linux-next: build failure after merge of the scsi tree

On Fri, 2012-07-20 at 10:41 +1000, Stephen Rothwell wrote: Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/base/dd.c:27:28: fatal error: scsi/scsi_scan.h: No such file or directory Caused by commit eea03c20ae38 (Make

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/base/dd.c:27:28: fatal error: scsi/scsi_scan.h: No such file or directory Caused by commit eea03c20ae38 ("Make wait_for_device_probe() also do scsi_complete_async_scans()") from

linux-next: build failure after merge of the scsi tree

Hi James, After merging the scsi tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: drivers/base/dd.c:27:28: fatal error: scsi/scsi_scan.h: No such file or directory Caused by commit eea03c20ae38 (Make wait_for_device_probe() also do scsi_complete_async_scans()) from