All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ed Lin - PTU <ed.lin@promise.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	device-mapper development <dm-devel@redhat.com>,
	linux-scsi@vger.kernel.org,
	Promise_Linux <Promise_Linux@promise.com>,
	stable@kernel.org
Subject: Re: [dm-devel] QUEUE_FLAG_CLUSTER?
Date: Tue, 30 Nov 2010 13:40:56 -0500	[thread overview]
Message-ID: <yq11v627iyv.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <85ABFDC4641C4847BA6088F2982EFD8F04A4A669@nonamew.ptu.promise.com> (Ed Lin's message of "Mon, 29 Nov 2010 11:08:50 -0800")

>>>>> "Ed" == "Ed Lin <- PTU" <ed.lin@promise.com>> writes:

Ed> Is it possible to port the patch to previous kernels?

There's a bit of fuzz due to some of the discard changes and the sysfs
export of the segment size. But the core of the patch is the same.

http://git.kernel.org/pub/scm/linux/kernel/git/mkp/linux-2.6-mkp.git
git://git.kernel.org/pub/scm/linux/kernel/git/mkp/linux-2.6-mkp.git

I've created three branches:

for-stable-2.6.32.y
for-stable-2.6.35.y
for-stable-2.6.36.y

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2010-11-30 18:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-20  1:24 QUEUE_FLAG_CLUSTER? Ed Lin - PTU
2010-11-25 15:21 ` [dm-devel] QUEUE_FLAG_CLUSTER? Martin K. Petersen
2010-11-25 16:35   ` block: Deprecate QUEUE_FLAG_CLUSTER and use queue_limits instead Martin K. Petersen
2010-11-25 18:43     ` Jens Axboe
2010-11-26  0:37       ` Martin K. Petersen
2010-11-26  2:28         ` Mike Snitzer
2010-11-26  2:53           ` Martin K. Petersen
2010-11-26  9:00           ` Jens Axboe
2010-12-01 18:43         ` Jens Axboe
2010-11-29 19:08   ` [dm-devel] QUEUE_FLAG_CLUSTER? Ed Lin - PTU
2010-11-30 18:40     ` Martin K. Petersen [this message]
2010-12-07 21:48       ` [stable] " Greg KH

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=yq11v627iyv.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=Promise_Linux@promise.com \
    --cc=dm-devel@redhat.com \
    --cc=ed.lin@promise.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stable@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.