On Wed, Feb 10 2021 at 10:36pm -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/md/dm-linear.c:234:3: error: 'struct target_type' has no member named
> 'report_zones'
> 234 |
Hi Mike,
On Thu, 6 Dec 2018 08:41:06 -0500 Mike Snitzer wrote:
>
> Sorry for the trouble. I'll get this fixed up.
Thanks.
--
Cheers,
Stephen Rothwell
pgpJGFtEii3Nl.pgp
Description: OpenPGP digital signature
Hi Mike,
On Thu, 6 Dec 2018 08:41:06 -0500 Mike Snitzer wrote:
>
> Sorry for the trouble. I'll get this fixed up.
Thanks.
--
Cheers,
Stephen Rothwell
pgpJGFtEii3Nl.pgp
Description: OpenPGP digital signature
On Thu, Dec 06 2018 at 1:21am -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
...
> Caused by commit
>
> 3a657cf59109 ("block: switch to per-cpu in-flight counters")
>
> This build
On Thu, Dec 06 2018 at 1:21am -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
...
> Caused by commit
>
> 3a657cf59109 ("block: switch to per-cpu in-flight counters")
>
> This build
Hi Jens,
On Thu, 31 May 2018 09:02:01 -0600 Jens Axboe wrote:
>
> Talked to Mike offline, but for Stephen's sake I'll reiterate here
> too. Since I'm assuming that dm-writecache is the only problematic
> user here, and since Mike based dm-4.18 on the block tree, I considered
> it saner to leave
Hi Jens,
On Thu, 31 May 2018 09:02:01 -0600 Jens Axboe wrote:
>
> Talked to Mike offline, but for Stephen's sake I'll reiterate here
> too. Since I'm assuming that dm-writecache is the only problematic
> user here, and since Mike based dm-4.18 on the block tree, I considered
> it saner to leave
On 5/31/18 8:22 AM, Jens Axboe wrote:
> On 5/31/18 8:20 AM, Jens Axboe wrote:
>> On 5/31/18 6:10 AM, Mike Snitzer wrote:
>>> On Thu, May 31 2018 at 12:35am -0400,
>>> Jens Axboe wrote:
>>>
On May 30, 2018, at 10:23 PM, Stephen Rothwell
wrote:
>
> Hi all,
>
> After
On 5/31/18 8:22 AM, Jens Axboe wrote:
> On 5/31/18 8:20 AM, Jens Axboe wrote:
>> On 5/31/18 6:10 AM, Mike Snitzer wrote:
>>> On Thu, May 31 2018 at 12:35am -0400,
>>> Jens Axboe wrote:
>>>
On May 30, 2018, at 10:23 PM, Stephen Rothwell
wrote:
>
> Hi all,
>
> After
On 5/31/18 8:20 AM, Jens Axboe wrote:
> On 5/31/18 6:10 AM, Mike Snitzer wrote:
>> On Thu, May 31 2018 at 12:35am -0400,
>> Jens Axboe wrote:
>>
>>> On May 30, 2018, at 10:23 PM, Stephen Rothwell
>>> wrote:
Hi all,
After merging the device-mapper tree, today's linux-next
On 5/31/18 8:20 AM, Jens Axboe wrote:
> On 5/31/18 6:10 AM, Mike Snitzer wrote:
>> On Thu, May 31 2018 at 12:35am -0400,
>> Jens Axboe wrote:
>>
>>> On May 30, 2018, at 10:23 PM, Stephen Rothwell
>>> wrote:
Hi all,
After merging the device-mapper tree, today's linux-next
On 5/31/18 6:10 AM, Mike Snitzer wrote:
> On Thu, May 31 2018 at 12:35am -0400,
> Jens Axboe wrote:
>
>> On May 30, 2018, at 10:23 PM, Stephen Rothwell wrote:
>>>
>>> Hi all,
>>>
>>> After merging the device-mapper tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>>
On 5/31/18 6:10 AM, Mike Snitzer wrote:
> On Thu, May 31 2018 at 12:35am -0400,
> Jens Axboe wrote:
>
>> On May 30, 2018, at 10:23 PM, Stephen Rothwell wrote:
>>>
>>> Hi all,
>>>
>>> After merging the device-mapper tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>>
On Thu, May 31 2018 at 12:35am -0400,
Jens Axboe wrote:
> On May 30, 2018, at 10:23 PM, Stephen Rothwell wrote:
> >
> > Hi all,
> >
> > After merging the device-mapper tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/md/dm-writecache.c: In function
On Thu, May 31 2018 at 12:35am -0400,
Jens Axboe wrote:
> On May 30, 2018, at 10:23 PM, Stephen Rothwell wrote:
> >
> > Hi all,
> >
> > After merging the device-mapper tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/md/dm-writecache.c: In function
Hi Jens,
On Wed, 30 May 2018 22:35:40 -0600 Jens Axboe wrote:
>
> I’ll drop the last patch, we can do that at the end of the merge window
> instead.
Thanks.
--
Cheers,
Stephen Rothwell
pgpPUddo5Ay6c.pgp
Description: OpenPGP digital signature
Hi Jens,
On Wed, 30 May 2018 22:35:40 -0600 Jens Axboe wrote:
>
> I’ll drop the last patch, we can do that at the end of the merge window
> instead.
Thanks.
--
Cheers,
Stephen Rothwell
pgpPUddo5Ay6c.pgp
Description: OpenPGP digital signature
On May 30, 2018, at 10:23 PM, Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/md/dm-writecache.c: In function 'writecache_dtr':
> drivers/md/dm-writecache.c:1799:3: error: implicit
On May 30, 2018, at 10:23 PM, Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/md/dm-writecache.c: In function 'writecache_dtr':
> drivers/md/dm-writecache.c:1799:3: error: implicit
On 03/26/18 19:39, Stephen Rothwell wrote:
diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index d5db9df7ea4b..0589a4da12bb 100644
--- a/drivers/md/dm-table.c
+++ b/drivers/md/dm-table.c
@@ -1896,7 +1896,7 @@ void dm_table_set_restrictions(struct dm_table *t, struct
request_queue *q,
On 03/26/18 19:39, Stephen Rothwell wrote:
diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index d5db9df7ea4b..0589a4da12bb 100644
--- a/drivers/md/dm-table.c
+++ b/drivers/md/dm-table.c
@@ -1896,7 +1896,7 @@ void dm_table_set_restrictions(struct dm_table *t, struct
request_queue *q,
On Fri, Jun 09 2017 at 12:28am -0400,
Damien Le Moal wrote:
> Stephen,
>
> On 6/9/17 12:12, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the device-mapper tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> >
On Fri, Jun 09 2017 at 12:28am -0400,
Damien Le Moal wrote:
> Stephen,
>
> On 6/9/17 12:12, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the device-mapper tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/md/dm-zoned-target.c:947:2: error:
Stephen,
On 6/9/17 12:12, Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/md/dm-zoned-target.c:947:2: error: unknown field 'suspend' specified
> in initializer
> .suspend =
Stephen,
On 6/9/17 12:12, Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/md/dm-zoned-target.c:947:2: error: unknown field 'suspend' specified
> in initializer
> .suspend =
On Thu, Mar 03 2016 at 9:59pm -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/md/dm.c: In function '__split_and_process_non_flush':
>
On Thu, Mar 03 2016 at 9:59pm -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/md/dm.c: In function '__split_and_process_non_flush':
> drivers/md/dm.c:1761:6: error: 'ret'
On Sun, Nov 01 2015 at 5:43am -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/md/dm-mpath.c: In function 'multipath_prepare_ioctl':
> drivers/md/dm-mpath.c:1570:41: error:
On Sun, Nov 01 2015 at 5:43am -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/md/dm-mpath.c: In function 'multipath_prepare_ioctl':
>
On 05/22/2015 07:26 AM, Mike Snitzer wrote:
On Fri, May 22 2015 at 8:49am -0400,
Mike Snitzer wrote:
On Thu, May 21 2015 at 11:27pm -0400,
Stephen Rothwell wrote:
Hi all,
After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
On Fri, May 22 2015 at 8:49am -0400,
Mike Snitzer wrote:
> On Thu, May 21 2015 at 11:27pm -0400,
> Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the device-mapper tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > block/bio.c:310:20: error:
On Thu, May 21 2015 at 11:27pm -0400,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> block/bio.c:310:20: error: redefinition of 'bio_inc_remaining'
> static inline void
On Thu, May 21 2015 at 11:27pm -0400,
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
block/bio.c:310:20: error: redefinition of 'bio_inc_remaining'
static inline void
On Fri, May 22 2015 at 8:49am -0400,
Mike Snitzer snit...@redhat.com wrote:
On Thu, May 21 2015 at 11:27pm -0400,
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
On 05/22/2015 07:26 AM, Mike Snitzer wrote:
On Fri, May 22 2015 at 8:49am -0400,
Mike Snitzer snit...@redhat.com wrote:
On Thu, May 21 2015 at 11:27pm -0400,
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the device-mapper tree, today's linux-next build (powerpc
On Tue, Jan 14 2014 at 10:52pm -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> ERROR: ".dm_bufio_get_device_size" [drivers/md/dm-snapshot.ko] undefined!
> ERROR: ".dm_bufio_release"
On Tue, Jan 14 2014 at 10:52pm -0500,
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ERROR: .dm_bufio_get_device_size [drivers/md/dm-snapshot.ko] undefined!
ERROR:
On 11/05/2013 03:42 PM, Stephen Rothwell wrote:
> Hi Jens,
>
> On Tue, 05 Nov 2013 09:22:11 -0700 Jens Axboe wrote:
>>
>> Just a heads up that I plan on sending the block bits shortly, hopefully
>> merging sooner rather than later. This round is huge, so I'd like to get
>> it in asap.
>
> Given
Hi Jens,
On Tue, 05 Nov 2013 09:22:11 -0700 Jens Axboe wrote:
>
> Just a heads up that I plan on sending the block bits shortly, hopefully
> merging sooner rather than later. This round is huge, so I'd like to get
> it in asap.
Given the problems we have seen since the inclusion into linux-next
On 11/05/2013 05:54 AM, Mike Snitzer wrote:
> On Mon, Nov 04 2013 at 10:32pm -0500,
> Stephen Rothwell wrote:
>
>> Hi Mike,
>>
>> On Mon, 4 Nov 2013 22:20:54 -0500 Mike Snitzer wrote:
>>>
>>> On Mon, Nov 04 2013 at 9:51pm -0500,
>>> Stephen Rothwell wrote:
>>>
After merging the
On Mon, Nov 04 2013 at 10:32pm -0500,
Stephen Rothwell wrote:
> Hi Mike,
>
> On Mon, 4 Nov 2013 22:20:54 -0500 Mike Snitzer wrote:
> >
> > On Mon, Nov 04 2013 at 9:51pm -0500,
> > Stephen Rothwell wrote:
> >
> > > After merging the device-mapper tree, today's linux-next build (x86_64
> > >
On Mon, Nov 04 2013 at 10:32pm -0500,
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Mike,
On Mon, 4 Nov 2013 22:20:54 -0500 Mike Snitzer snit...@redhat.com wrote:
On Mon, Nov 04 2013 at 9:51pm -0500,
Stephen Rothwell s...@canb.auug.org.au wrote:
After merging the device-mapper
On 11/05/2013 05:54 AM, Mike Snitzer wrote:
On Mon, Nov 04 2013 at 10:32pm -0500,
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Mike,
On Mon, 4 Nov 2013 22:20:54 -0500 Mike Snitzer snit...@redhat.com wrote:
On Mon, Nov 04 2013 at 9:51pm -0500,
Stephen Rothwell s...@canb.auug.org.au
Hi Jens,
On Tue, 05 Nov 2013 09:22:11 -0700 Jens Axboe ax...@kernel.dk wrote:
Just a heads up that I plan on sending the block bits shortly, hopefully
merging sooner rather than later. This round is huge, so I'd like to get
it in asap.
Given the problems we have seen since the inclusion into
On 11/05/2013 03:42 PM, Stephen Rothwell wrote:
Hi Jens,
On Tue, 05 Nov 2013 09:22:11 -0700 Jens Axboe ax...@kernel.dk wrote:
Just a heads up that I plan on sending the block bits shortly, hopefully
merging sooner rather than later. This round is huge, so I'd like to get
it in asap.
Hi Mike,
On Mon, 4 Nov 2013 22:20:54 -0500 Mike Snitzer wrote:
>
> On Mon, Nov 04 2013 at 9:51pm -0500,
> Stephen Rothwell wrote:
>
> > After merging the device-mapper tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/md/dm-cache-target.c: In function
On Mon, Nov 04 2013 at 9:51pm -0500,
Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/md/dm-cache-target.c: In function 'bio_writes_complete_block':
> drivers/md/dm-cache-target.c:1020:7:
On Mon, Nov 04 2013 at 9:51pm -0500,
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the device-mapper tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/md/dm-cache-target.c: In function 'bio_writes_complete_block':
Hi Mike,
On Mon, 4 Nov 2013 22:20:54 -0500 Mike Snitzer snit...@redhat.com wrote:
On Mon, Nov 04 2013 at 9:51pm -0500,
Stephen Rothwell s...@canb.auug.org.au wrote:
After merging the device-mapper tree, today's linux-next build (x86_64
allmodconfig) failed like this:
49 matches
Mail list logo