mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2/4] 2.6.22-rc3: known regressions
Date: Thu, 31 May 2007 15:22:07 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0705311516350.26602@woody.linux-foundation.org> (raw)
In-Reply-To: <20070531220833.GA10867@beardog.cca.cpqcorp.net>



On Thu, 31 May 2007, Mike Miller (OS Dev) wrote:

> On Wed, May 30, 2007 at 07:22:14PM -0700, Linus Torvalds wrote:
> > 
> > 
> > On Tue, 29 May 2007, Michal Piotrowski wrote:
> > > 
> > > Subject    : Oops on 2.6.22-rc2 when unloading the cciss driver
> > > References : http://lkml.org/lkml/2007/5/24/172
> > > Submitter  : Mike Miller (OS Dev) <mikem@beardog.cca.cpqcorp.net>
> > > Status     : Unknown
> > 
> > I thought this one should be fixed by commit e9ca75b53. Not so?
> 
> I apologize for the slow response. I also apologize that I don't know enough
> about git to figure out what commit e9ca75b53 does.

Even without git, you can use the kernel.org gitweb install:

	http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e9ca75b53

(where the "h=...." is the magic part - pick any commit SHA1 you want, 
including short-hand ones like the one I gave).

With git, you just do

	git show e9ca75b53

to see a particular named commit.

> I submitted a fix that was blessed by Eric B. that fixed that Oops.

Ok, I don't think I have anything like that. The one I pointed to is the 
one by Gerald Britton, acked by you ..

But I now realize that that commit was already in -rc2. In fact, it's just 
before the -rc2 release. So while it claims to fix one oops on shutdown, 
it may be the _cause_ of the oops on mudule unload.

		Linus

  reply	other threads:[~2007-05-31 22:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <465C188F.9000900@googlemail.com>
2007-05-29 12:52 ` [3/4] " Michal Piotrowski
2007-05-29 21:47   ` [PATCH] NOHZ: prevent multiplication overflow - stop timer for huge timeouts Thomas Gleixner
2007-05-29 23:02     ` David Miller
2007-05-31  2:33   ` [3/4] 2.6.22-rc3: known regressions Linus Torvalds
2007-05-31  4:51     ` Antonino A. Daplas
2007-05-31  5:54       ` Tero Roponen
2007-05-31  6:04         ` [PATCH] neofb: Fix pseudo_palette array overrun in neofb_setcolreg Antonino A. Daplas
2007-06-05 11:09         ` Antonino A. Daplas
2007-06-05 11:34         ` [PATCH] [RESEND] " Antonino A. Daplas
2007-05-29 12:53 ` [4/4] 2.6.22-rc3: known regressions Michal Piotrowski
2007-06-09 11:38   ` Mauro Carvalho Chehab
2007-05-29 12:56 ` [2/4] " Michal Piotrowski
2007-05-29 15:01   ` Stephen Hemminger
2007-05-31  2:22   ` Linus Torvalds
2007-05-31 22:08     ` Mike Miller (OS Dev)
2007-05-31 22:22       ` Linus Torvalds [this message]
2007-05-31 22:39         ` Mike Miller (OS Dev)
2007-05-31 22:50           ` Andrew Morton
2007-05-31 23:12             ` Linus Torvalds
2007-05-31 23:17               ` Roland Dreier
2007-05-31 23:34                 ` Andrew Morton

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=alpine.LFD.0.98.0705311516350.26602@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=mikem@beardog.cca.cpqcorp.net \
    /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

all inboxes | Powered by JetHome®