From: David Miller <davem@davemloft.net>
To: James.Bottomley@HansenPartnership.com
Cc: mpatocka@redhat.com, fujita.tomonori@lab.ntt.co.jp,
jens.axboe@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH] block: fix q->max_segment_size checking in blk_recalc_rq_segments about VMERGE
Date: Sat, 19 Jul 2008 21:07:37 -0700 (PDT) [thread overview]
Message-ID: <20080719.210737.197246608.davem@davemloft.net> (raw)
In-Reply-To: <1216520228.3376.33.camel@localhost.localdomain>
From: James Bottomley <James.Bottomley@HansenPartnership.com>
Date: Sat, 19 Jul 2008 21:17:08 -0500
> Try this patch
I'd rather remove the vmerge code, it doesn't buy us
anything, and for something so complex and so hard to
keep working correctly it's existence is far from
justified these days.
next prev parent reply other threads:[~2008-07-20 4:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 10:44 [PATCH] block: fix q->max_segment_size checking in blk_recalc_rq_segments about VMERGE FUJITA Tomonori
2008-07-15 13:37 ` Mikulas Patocka
2008-07-15 14:20 ` FUJITA Tomonori
2008-07-15 14:37 ` Mikulas Patocka
2008-07-15 15:30 ` FUJITA Tomonori
2008-07-15 15:46 ` Mikulas Patocka
2008-07-16 0:34 ` FUJITA Tomonori
2008-07-16 18:02 ` Mikulas Patocka
2008-07-17 4:14 ` FUJITA Tomonori
2008-07-17 11:50 ` Mikulas Patocka
2008-07-17 13:18 ` FUJITA Tomonori
2008-07-17 13:27 ` Boaz Harrosh
2008-07-17 13:56 ` James Bottomley
2008-07-19 7:28 ` David Miller
2008-07-20 1:45 ` Mikulas Patocka
2008-07-20 2:17 ` James Bottomley
2008-07-20 4:07 ` David Miller [this message]
2008-07-20 14:52 ` James Bottomley
2008-07-20 17:23 ` David Miller
2008-07-20 17:33 ` James Bottomley
2008-07-24 15:07 ` Mikulas Patocka
2008-07-24 15:28 ` James Bottomley
2008-07-24 16:34 ` Mikulas Patocka
2008-07-24 16:52 ` James Bottomley
2008-07-24 21:49 ` Mikulas Patocka
2008-07-24 21:53 ` David Miller
2008-07-25 3:47 ` James Bottomley
2008-07-25 5:21 ` David Miller
2008-07-25 2:26 ` FUJITA Tomonori
2008-07-25 2:40 ` [PATCH] block: fix q->max_segment_size checking in blk_recalc_rq_segments John David Anglin
2008-07-20 5:54 ` [PATCH] block: fix q->max_segment_size checking in blk_recalc_rq_segments about VMERGE David Miller
2008-07-15 14:50 ` James Bottomley
2008-07-15 15:24 ` Mikulas Patocka
2008-07-15 15:41 ` James Bottomley
2008-07-15 15:58 ` Mikulas Patocka
2008-07-15 16:07 ` James Bottomley
2008-07-15 16:20 ` Mikulas Patocka
2008-07-15 16:36 ` James Bottomley
2008-07-15 21:50 ` Mikulas Patocka
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=20080719.210737.197246608.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mpatocka@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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