public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Daniel Drake <dsd@gentoo.org>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	linux-stable <stable@kernel.org>, Dave Jones <davej@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [stable]  libata spindown patches for 2.6.21-stable
Date: Thu, 14 Jun 2007 11:12:10 -0700	[thread overview]
Message-ID: <20070614181210.GA11421@kroah.com> (raw)
In-Reply-To: <46717F7E.2040507@gentoo.org>

On Thu, Jun 14, 2007 at 01:48:46PM -0400, Daniel Drake wrote:
>  Greg KH wrote:
> > I think it looks way too big.
> 
>  Agreed (otherwise I would have submitted the patches already).
> 
> > If there are smaller patches, it might be a bit more reasonable.
> 
>  It may be possible to get rid of the couple of unrelated ones (sd printing, 
>  SCSI constants). These were required for the real patches to be able to 
>  build, but it would probably be easy to modify the real patches to build 
>  against kernels without those otherwise unrelated patches.
> 
> > Are there reported bugs that this patchset fixes?
> 
>  Yes, but they are not regressions - libata has never done this right until 
>  now.
> 
>  Here are a few:
>  https://bugs.gentoo.org/show_bug.cgi?id=174373
>  http://bugzilla.kernel.org/show_bug.cgi?id=7674
>  http://bugzilla.kernel.org/show_bug.cgi?id=7838
>  https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/67810

Ok, if people want to post some smaller patches to the stable team,
we'll be glad to consider them.

thanks,

greg k-h

      reply	other threads:[~2007-06-14 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 16:01 [stable] libata spindown patches for 2.6.21-stable Chuck Ebbert
2007-06-14 17:30 ` Greg KH
2007-06-14 17:45   ` Henrique de Moraes Holschuh
2007-06-14 17:48   ` Daniel Drake
2007-06-14 18:12     ` Greg KH [this message]

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=20070614181210.GA11421@kroah.com \
    --to=greg@kroah.com \
    --cc=cebbert@redhat.com \
    --cc=davej@redhat.com \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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