From: Andrew Morton <akpm@linux-foundation.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: petkovbb@gmail.com, gregkh@suse.de, ptesarik@suse.cz,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
jens.axboe@oracle.com, jack@suse.cz
Subject: Re: [PATCH] ide-cd: fix endianity for the error message in cdrom_read_capacity
Date: Wed, 30 Jul 2008 13:02:55 -0700 [thread overview]
Message-ID: <20080730130255.9538678a.akpm@linux-foundation.org> (raw)
In-Reply-To: <200807302125.54124.bzolnier@gmail.com>
On Wed, 30 Jul 2008 21:25:53 +0200
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> > > Bart owns this patch now. It got lost for a month and it has already
> > > been fixed twice and it is also on the route to 2.6.25.x and 2.6.26.x,
> > > so it'll get complicated. Not a happy little patch.
> >
> > Greg, can you please apply this one on top of -stable.
>
> The usual policy is to not apply to -stable patches which are not in
> Linus' tree so please notify stable@kernelorg team after patch hits
> mainline.
Please put a Cc: <stable@kernel.org> into the changelog. Then the
stable people will notice it when Linus commits it.
next prev parent reply other threads:[~2008-07-30 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 8:10 [PATCH] ide-cd: fix endianity for the error message in cdrom_read_capacity Petr Tesarik
2008-07-30 8:18 ` Andrew Morton
2008-07-30 8:52 ` Boris Petkov
2008-07-30 16:33 ` Greg KH
2008-07-30 19:12 ` Borislav Petkov
2008-07-30 20:58 ` Greg KH
2008-07-30 20:58 ` Greg KH
2008-07-31 3:32 ` Borislav Petkov
2008-07-30 19:27 ` Borislav Petkov
2008-07-30 19:25 ` Bartlomiej Zolnierkiewicz
2008-07-30 20:02 ` Andrew Morton [this message]
2008-07-30 21:23 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2008-07-30 7:42 Petr Tesarik
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=20080730130255.9538678a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=gregkh@suse.de \
--cc=jack@suse.cz \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@gmail.com \
--cc=ptesarik@suse.cz \
/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.