All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: satha kottidi <satha_koti@yahoo.co.in>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Need information regarding RAID 6 Async APIs for kernel version 2.6.27
Date: Fri, 29 May 2009 12:13:50 -0700	[thread overview]
Message-ID: <4A2033EE.4040302@intel.com> (raw)
In-Reply-To: <264829.64332.qm@web94806.mail.in2.yahoo.com>

satha kottidi wrote:
> Hi all,
> 
> Dan thanks for your recommendations, I followed it, got the present 
> running branch and working on it.
> 
> I have one more rquest, presently I want to run the Async_tx APIs 
> (RAID6) in kernel 2.6.27, Is any suggestions for further process.
> 
> Is the only way I have to extract the changes in the branch and applied 
> to my kernel, or any other ways.
> 
> Can you please help me in this regard also.

Backporting is a black art, and is rarely straightforward.  In a perfect 
world you could use Stacked GIT to rebase all the relevant changes onto 
a 2.6.27 base with a script like:

git log --reverse v2.6.27..async_tx/raid6 --no-merges\
--pretty=format:"%H" drivers/md/md.c drivers/md/raid5.c drivers/dma/ \
crypto/async_tx/ > commits

git checkout -b 2.6.27-raid6 v2.6.27
stg init
cat commits | while read commit;
do
	stg pick $commit
done

...but there is a high likelihood to encounter merge conflicts and other 
  cross-tree dependencies especially when trying to backport across ~3 
kernel versions.

Good luck,
Dan

       reply	other threads:[~2009-05-29 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <264829.64332.qm@web94806.mail.in2.yahoo.com>
2009-05-29 19:13 ` Dan Williams [this message]
2009-05-28 17:57 Need information regarding RAID 6 Async APIs for kernel version 2.6.27 Koti
2009-05-28 22:56 ` Dan Williams

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=4A2033EE.4040302@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=satha_koti@yahoo.co.in \
    /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.