From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, matthew@wil.cx,
linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Anders Henke <anders.henke@1und1.de>,
stable@kernel.org
Subject: Re: [PATCH] dpt_i2o: don't set DMA_64BIT_MASK [was: Re: [stable] broken dpt_i2o in 2.6.23 (was: ext2 check page: bad entry in directory) (fwd)]
Date: Thu, 13 Dec 2007 07:58:01 -0500 [thread overview]
Message-ID: <1197550681.3154.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20071213101144.GA61767@xs4all.net>
On Thu, 2007-12-13 at 11:11 +0100, Miquel van Smoorenburg wrote:
> According to Greg KH:
> > So, what should be added to 2.6.23-stable then? And, can I get a real
> > changelog entry for it?
>
> This is suitable for both 2.6.23.x and 2.6.24-rc5 :
>
> linux-2.6-dpt_i2o-no-dma64.patch
Actually, this one's already queued:
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commit;h=a066b307861238c1970310579c0bc2fe8c8dca51
James
next prev parent reply other threads:[~2007-12-13 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 10:58 broken dpt_i2o in 2.6.23 (was: ext2 check page: bad entry in directory) (fwd) Anders Henke
2007-12-12 11:38 ` Andrew Morton
2007-12-12 13:07 ` Miquel van Smoorenburg
2007-12-12 13:43 ` Anders Henke
2007-12-12 19:16 ` Andrew Morton
2007-12-12 19:54 ` James Bottomley
2007-12-12 22:16 ` [stable] " Greg KH
2007-12-13 10:11 ` [PATCH] dpt_i2o: don't set DMA_64BIT_MASK [was: Re: [stable] broken dpt_i2o in 2.6.23 (was: ext2 check page: bad entry in directory) (fwd)] Miquel van Smoorenburg
2007-12-13 12:58 ` James Bottomley [this message]
2007-12-12 14:17 ` broken dpt_i2o in 2.6.23 (was: ext2 check page: bad entry in directory) (fwd) Anders Henke
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=1197550681.3154.7.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=anders.henke@1und1.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=miquels@cistron.nl \
--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).