Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-23 Thread Dan Carpenter
On Mon, Apr 22, 2013 at 07:56:19PM -0700, Christopher Li wrote: > On Mon, Apr 22, 2013 at 4:56 PM, Andrew Morton > wrote: > > I think doing IS_ERR() and PTR_ERR() on __iomem pointers is a natural > > thing, and we should be able to do this without adding call-site > > trickery to make sparse

Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-23 Thread Dan Carpenter
On Mon, Apr 22, 2013 at 07:56:19PM -0700, Christopher Li wrote: On Mon, Apr 22, 2013 at 4:56 PM, Andrew Morton a...@linux-foundation.org wrote: I think doing IS_ERR() and PTR_ERR() on __iomem pointers is a natural thing, and we should be able to do this without adding call-site trickery to

Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-22 Thread Christopher Li
On Mon, Apr 22, 2013 at 4:56 PM, Andrew Morton wrote: > I think doing IS_ERR() and PTR_ERR() on __iomem pointers is a natural > thing, and we should be able to do this without adding call-site > trickery to make sparse happy. > > Is there some sort of annotation which we can add to the >

Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-22 Thread Fengguang Wu
On Mon, Apr 22, 2013 at 04:56:29PM -0700, Andrew Morton wrote: > On Sat, 20 Apr 2013 07:54:34 +0800 kbuild test robot > wrote: > > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > akpm > > head: c9941b7ec7840ad33f5822c7f238157558d40132 > > commit:

Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-22 Thread Andrew Morton
On Sat, 20 Apr 2013 07:54:34 +0800 kbuild test robot wrote: > tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm > head: c9941b7ec7840ad33f5822c7f238157558d40132 > commit: d5e42b5769899607e1e4b0c9200340d24f370e8c [798/1000] rtc: rtc-ds1286: > use devm_*()

Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-22 Thread Andrew Morton
On Sat, 20 Apr 2013 07:54:34 +0800 kbuild test robot fengguang...@intel.com wrote: tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm head: c9941b7ec7840ad33f5822c7f238157558d40132 commit: d5e42b5769899607e1e4b0c9200340d24f370e8c [798/1000] rtc: rtc-ds1286: use

Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-22 Thread Fengguang Wu
On Mon, Apr 22, 2013 at 04:56:29PM -0700, Andrew Morton wrote: On Sat, 20 Apr 2013 07:54:34 +0800 kbuild test robot fengguang...@intel.com wrote: tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm head: c9941b7ec7840ad33f5822c7f238157558d40132 commit:

Re: [next:akpm 798/1000] drivers/rtc/rtc-ds1286.c:343:24: sparse: incorrect type in argument 1 (different address spaces)

2013-04-22 Thread Christopher Li
On Mon, Apr 22, 2013 at 4:56 PM, Andrew Morton a...@linux-foundation.org wrote: I think doing IS_ERR() and PTR_ERR() on __iomem pointers is a natural thing, and we should be able to do this without adding call-site trickery to make sparse happy. Is there some sort of annotation which we can