linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Howard <faxguy@howardsilvan.com>
To: Asdo <asdo@shiftmail.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [Fwd: Re: BUG: soft lockup - CPU#0 stuck for 10s! [md2_raid1:358]]
Date: Wed, 21 Oct 2009 20:27:58 -0700	[thread overview]
Message-ID: <4ADFD13E.90900@howardsilvan.com> (raw)
In-Reply-To: <4ADEFFC9.10405@shiftmail.org>

Asdo wrote:
> Lee Howard wrote:
>
>> I've been deliberately monitoring the kernel via the git web 
>> interfaces, and I can't yet see the patch committed that supposedly 
>> fixed this.  (Please correct me if it was actually committed.)
>
> Somebody told it was fixed in 2.6.32. Have you checked that one?
>
> Would you mind to explain me HOW to check such a thing via web git? I 
> wanted to do this in the past but I didn't know how to do it...

I'm not sure that I was doing it the *right* way, but go to:

http://git.kernel.org/

Click on "md raid development 
<http://git.kernel.org/?p=linux/kernel/git/djbw/md.git;a=summary>".  
Then if you look at the bottom for "master" head you'll go to this link:

http://git.kernel.org/?p=linux/kernel/git/djbw/md.git;a=shortlog;h=refs/heads/master

Then click on "tree" ( 
http://git.kernel.org/?p=linux/kernel/git/djbw/md.git;a=tree;h=refs/heads/master;hb=refs/heads/master 
) to browse the repository tree.  Dig a little further, and go to 
drivers/md and you can see the change history in the various files to 
see if a patch has been applied.

Maybe that's the wrong way to do it, but that's how I was looking.

Thanks,

Lee.



  parent reply	other threads:[~2009-10-22  3:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 12:34 [Fwd: Re: BUG: soft lockup - CPU#0 stuck for 10s! [md2_raid1:358]] Asdo
2009-10-21 21:48 ` Neil Brown
2009-10-22  3:29   ` Lee Howard
2009-10-22  3:27 ` Lee Howard [this message]
2009-10-26 17:28   ` 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=4ADFD13E.90900@howardsilvan.com \
    --to=faxguy@howardsilvan.com \
    --cc=asdo@shiftmail.org \
    --cc=linux-raid@vger.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 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).