From: Neil Brown <neilb@suse•de>
To: "Martin K. Petersen" <martin.petersen@oracle•com>
Cc: Jens Axboe <jens.axboe@oracle•com>, linux-next@vger•kernel.org
Subject: Re: linux-next: md tree build failure
Date: Thu, 4 Jun 2009 14:06:43 +1000 [thread overview]
Message-ID: <18983.18515.445191.401600@notabene.brown> (raw)
In-Reply-To: message from Martin K. Petersen on Wednesday June 3
On Wednesday June 3, martin.petersen@oracle•com wrote:
>
> James often rebases against Jens' tree because there's frequently
> dependencies between between block and SCSI during the merge. I suggest
> you do the same.
OK, I've just rebased my for-next tree against Jens' for-next, and
fixed the compile error with this incremental patch
--- a/drivers/md/raid0.c
+++ b/drivers/md/raid0.c
@@ -240,7 +240,7 @@ static int create_strip_zones(mddev_t *mddev)
* now since we have the hard sector sizes, we can make sure
* chunk size is a multiple of that sector size
*/
- if (mddev->chunk_size % mddev->queue->hardsect_size) {
+ if (mddev->chunk_size % queue_logical_block_size(mddev->queue)) {
printk(KERN_ERR "%s chunk_size of %d not valid\n",
mdname(mddev),
mddev->chunk_size);
I assume that is the preferred usage?
Thanks,
NeilBrown
next prev parent reply other threads:[~2009-06-04 4:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 5:33 linux-next: md tree build failure Stephen Rothwell
2009-05-25 6:15 ` Jens Axboe
2009-05-25 11:44 ` Martin K. Petersen
2009-06-01 4:42 ` Stephen Rothwell
2009-06-01 5:13 ` Martin K. Petersen
2009-06-01 5:33 ` NeilBrown
[not found] ` <yq1prdm6jn1.fsf@sermon.lab.mkp.net>
2009-06-04 4:06 ` Neil Brown [this message]
2009-06-04 4:17 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2009-03-11 5:27 Stephen Rothwell
2009-03-13 0:45 ` Neil Brown
2009-03-13 2:21 ` Stephen Rothwell
2009-03-10 5:47 Stephen Rothwell
2009-03-10 6:38 ` NeilBrown
2009-03-10 6:48 ` Stephen Rothwell
2008-10-15 9:09 Stephen Rothwell
2008-10-15 10:55 ` Neil Brown
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=18983.18515.445191.401600@notabene.brown \
--to=neilb@suse$(echo .)de \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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