All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
	Alan Piszcz <ap@solarrain.com>,
	NetDEV list <netdev@vger.kernel.org>,
	xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 3.1-rc4: spectacular kernel errors / filesystem crash
Date: Tue, 13 Sep 2011 16:58:12 +0200	[thread overview]
Message-ID: <CAL4WiipmRyprf3nU-mgz8zE+n=Cy_Th=MT1JMnO=Qy_993++yw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1109130722210.21380@p34.internal.lan>

2011/9/13 Justin Piszcz <jpiszcz@lucidpixels.com>:
>

> I found this commit here:
> http://permalink.gmane.org/gmane.linux.kernel.pci/11700
>
> Applied:
> # patch -p1 < ../ed2888e906b56769b4ffabb9c577190438aa68b8.txt patching file
> drivers/pci/probe.c
>
>

Oh, I should have sent the git anchor you can use instead of searching the web ;

git pull https://github.com/torvalds/linux.git

WARNING: multiple messages have this Message-ID (diff)
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: NetDEV list <netdev@vger.kernel.org>,
	xfs@oss.sgi.com, Alan Piszcz <ap@solarrain.com>,
	linux-kernel@vger.kernel.org,
	Jesse Brandeburg <jesse.brandeburg@gmail.com>
Subject: Re: 3.1-rc4: spectacular kernel errors / filesystem crash
Date: Tue, 13 Sep 2011 16:58:12 +0200	[thread overview]
Message-ID: <CAL4WiipmRyprf3nU-mgz8zE+n=Cy_Th=MT1JMnO=Qy_993++yw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1109130722210.21380@p34.internal.lan>

2011/9/13 Justin Piszcz <jpiszcz@lucidpixels.com>:
>

> I found this commit here:
> http://permalink.gmane.org/gmane.linux.kernel.pci/11700
>
> Applied:
> # patch -p1 < ../ed2888e906b56769b4ffabb9c577190438aa68b8.txt patching file
> drivers/pci/probe.c
>
>

Oh, I should have sent the git anchor you can use instead of searching the web ;

git pull https://github.com/torvalds/linux.git

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-09-13 14:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-11  9:40 3.1-rc4: spectacular kernel errors / filesystem crash Justin Piszcz
2011-09-11  9:40 ` Justin Piszcz
2011-09-13  3:59 ` Jesse Brandeburg
2011-09-13  3:59   ` Jesse Brandeburg
2011-09-13  4:05   ` Eric Dumazet
2011-09-13  4:05     ` Eric Dumazet
2011-09-13 14:54     ` Justin Piszcz
2011-09-13 14:54       ` Justin Piszcz
2011-09-13 14:58       ` Eric Dumazet [this message]
2011-09-13 14:58         ` Eric Dumazet
2011-09-13 15:35       ` Jon Mason
2011-09-13 15:35         ` Jon Mason
2011-09-13 15:42         ` Justin Piszcz
2011-09-13 15:42           ` Justin Piszcz
2011-09-13 15:51           ` Jon Mason
2011-09-13 15:51             ` Jon Mason
2011-09-13 16:32             ` Justin Piszcz
2011-09-13 16:32               ` Justin Piszcz

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='CAL4WiipmRyprf3nU-mgz8zE+n=Cy_Th=MT1JMnO=Qy_993++yw@mail.gmail.com' \
    --to=eric.dumazet@gmail.com \
    --cc=ap@solarrain.com \
    --cc=jesse.brandeburg@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xfs@oss.sgi.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 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.