linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cláudio Martins" <ctpm@ist.utl.pt>
To: Michael Sallaway <michael@sallaway.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: status of sas1068 ata-passthrough bug?
Date: Wed, 3 Nov 2010 06:29:14 +0000	[thread overview]
Message-ID: <20101103062914.dac21685.ctpm@ist.utl.pt> (raw)
In-Reply-To: <4CD0D98D.3010503@sallaway.com>


On Wed, 03 Nov 2010 13:39:57 +1000 Michael Sallaway <michael@sallaway.com> wrote:
> 
> On 3/11/2010 1:20 PM, Cláudio Martins wrote:
> > Also, as a last resort, you could try to apply the patch and rebuild
> > using the sources of your favorite distro kernel. The patch is quite
> > simple, but be warned that the MPTSAS module also got some other
> > potentially interesting fixes on the 2.6.36 cycle.
> 
> Interesting.... where might I find out more info about that? (trying to 
> figure out if I should stay with .35 for now....)
> 

 Hi,

 What I do is follow Linus' git repository history periodically. I did
a "git clone" of his repo and now do a "git pull" from time to time.

 If you don't have done it already, taking a little time to get to know
the git basic commands is really useful for this kind of stuff. You
don't even need to know all the details of commiting, etc, but just
knowing how to use git-log and git-diff is already useful.

 For example, you would do

 git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
 cd linux-2.6
 git log --pretty=oneline drivers/message/fusion/

 Would give you commits related to mpt and mptsas drivers, while
ignoring unrelated commits. It is also easy to find out whether a given
release has a specific commit or not and find commits by a specific
author and much, much more.

 The commit messages also tend to explain quite well the issues fixed,
so it is usually enough to figure if a given commit is interesting or
not.

 git-diff will also generate a patch which is often good enough to
apply to an older kernel, provided the piece of code hasn't changed a
lot.

 Hope this helps.

Best regards

Cláudio

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-11-03  6:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 22:08 status of sas1068 ata-passthrough bug? Matt Garman
2010-11-02 22:05 ` Cláudio Martins
2010-11-03  3:00   ` Matt Garman
2010-11-03  3:20     ` Cláudio Martins
2010-11-03  3:39       ` Michael Sallaway
2010-11-03  6:29         ` Cláudio Martins [this message]
2010-11-03  6:33           ` Michael Sallaway
2010-11-04 12:50             ` Vincent Schut

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=20101103062914.dac21685.ctpm@ist.utl.pt \
    --to=ctpm@ist.utl.pt \
    --cc=linux-raid@vger.kernel.org \
    --cc=michael@sallaway.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;
as well as URLs for NNTP newsgroup(s).