linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: petkovbb@gmail.com, Greg KH <gregkh@suse.de>,
	stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	Petr Tesarik <ptesarik@suse.cz>,
	linux-kernel@vger.kernel.org, linux-ide@vg
Subject: Re: [PATCH] ide-cd: fix endianity for the error message in cdrom_read_capacity
Date: Wed, 30 Jul 2008 13:58:36 -0700	[thread overview]
Message-ID: <20080730205836.GA31232@kroah.com> (raw)
In-Reply-To: <20080730191257.GA1205@gollum.tnic>

On Wed, Jul 30, 2008 at 09:12:57PM +0200, Borislav Petkov wrote:
> On Wed, Jul 30, 2008 at 09:33:28AM -0700, Greg KH wrote:
> > On Wed, Jul 30, 2008 at 10:52:50AM +0200, Boris Petkov wrote:
> > > On Wed, Jul 30, 2008 at 10:18 AM, Andrew Morton
> > > <akpm@linux-foundation.org> wrote:
> > > > On Wed, 30 Jul 2008 10:10:06 +0200 Petr Tesarik <ptesarik@suse.cz> wrote:
> > > >
> > > >> Resent because of a typo in the LKML address. :(
> > > >
> > > > Thanks.
> > > >
> > > >>
> > > >> Aesthetic regards aside, commit e8e7b9eb11c34ee18bde8b7011af41938d1ad667
> > > >> still leaves a bug in the error message, because it uses the unconverted
> > > >> big-endian value for printk.
> > > >>
> > > >> Fix this by using a local variable in machine byte order. The result is
> > > >> correct, more readable, and also produces slightly shorter code on i386.
> > > >>
> > > >> Cc: Jens Axboe <jens.axboe@oracle.com>
> > > >> Cc: Jan Kara <jack@suse.cz>
> > > >> Signed-off-by: Petr Tesarik <ptesarik@suse.cz>
> > > 
> > > I definitely like this one better, thanks.
> > > 
> > > Acked-by: Borislav Petkov <petkovbb@gmail.com>
> > > 
> > > 
> > > >
> > > > 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.
> > 
> > What one?  Do you have a git commit id?
> 
> Oh, sorry about that. Ok, you should have in both 2.6.25 and .26 the patch with
> upstream commit id e8e7b9eb11c34ee18bde8b7011af41938d1ad667. I rediffed the new
> one on top, here's the 2.6.26 version, the 2.6.25 one follows.

I need the patch id when this goes to Linus, in his tree.  If you add
"cc: stable <stable@kernel.org>" to the signed-off-by area, when it gets
into Linus's tree, we will be automatically notified of it.

thanks,

greg k-h

  reply	other threads:[~2008-07-30 21:19 UTC|newest]

Thread overview: 12+ 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 [this message]
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
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=20080730205836.GA31232@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-ide@vg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petkovbb@gmail.com \
    --cc=ptesarik@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).