linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCHES] libata fixes
Date: Fri, 5 Dec 2003 10:44:28 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312051041000.9125@home.osdl.org> (raw)
In-Reply-To: <20031205181643.GA6877@gtf.org>



On Fri, 5 Dec 2003, Jeff Garzik wrote:
>
> Linus, please do a
>
> 	bk pull bk://gkernel.bkbits.net/libata-2.5
>
> This will update the following files:
>
>  drivers/scsi/libata-core.c  |   17 ++---
>  drivers/scsi/sata_promise.c |  128 +++++++++++++++++++++++++-------------------

Right now, I'm accepting one-liners that I think are "obvious" and also
"very important" (ie fixes for oopses that anybody can trigger, rather
than for example updates to one particular driver). So it sounds like I
might accept _one_ of these:

> <jgarzik@redhat.com> (03/12/05 1.1498)
>    [libata] fix use-after-free
>
>    Fixes oops some were seeing on module unload.
>
>    Caught by Jon Burgess.

If this is basically an obvious one-liner ("move a kfree")?

Andrew is still off, and he can make a decision independently, but right
now I'm not going to apply anything bigger.

		Linus

  reply	other threads:[~2003-12-05 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 18:16 [BK PATCHES] libata fixes Jeff Garzik
2003-12-05 18:44 ` Linus Torvalds [this message]
2003-12-05 18:47   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2003-11-08 17:26 Jeff Garzik
2003-11-08 20:16 ` Sergey Vlasov
2003-11-08 20:23   ` Jeff Garzik

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=Pine.LNX.4.58.0312051041000.9125@home.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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).