From: Mikael Pettersson <mikpe@it.uu.se>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
mikpe@it.uu.se, crmafra2@gmail.com, linux-kernel@vger.kernel.org,
James.Bottomley@HansenPartnership.com, htejun@gmail.com,
jens.axboe@oracle.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [BUG] 2.6.25-rc2-git3 broke cdrecord
Date: Mon, 3 Mar 2008 10:45:04 +0100 [thread overview]
Message-ID: <18379.51360.744676.894510@harpo.it.uu.se> (raw)
In-Reply-To: <47CBC014.9090309@s5r6.in-berlin.de>
Stefan Richter writes:
> FUJITA Tomonori wrote:
> > On Mon, 3 Mar 2008 02:48:23 +0100 (CET)
> > Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> >> CD burning still fails for me via ide-cd, although in a
> >> different way than without the patch. (Without the patch, ide-cd also
> >> fails like described by you for SATA.)
> >>
> >> With the patch, the failure is as follows. I don't know if this is
> >> related to the data length arithmetic or something entirely different;
> >> all I learned so far is that 2.6.24 works. Application log from
> >> 2.6.25-rc3 + Tejun's patch + Gentoo's cdrkit-1.1.6 + k3b:
> >
> > Can you try the following patch?
> >
> > http://lkml.org/lkml/2008/3/2/218
>
> Fails just like with Tejun's patch, alas.
At this point I must confess I feel very uneasy about this situation.
Dare I suggest the perhaps hereditary solution of reverting these
changes and doing them right after 2.6.25 final?
next prev parent reply other threads:[~2008-03-03 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200803022053.m22KrP2Y023591@harpo.it.uu.se>
2008-03-03 0:04 ` [BUG] 2.6.25-rc2-git3 broke cdrecord James Bottomley
[not found] ` <20080302233415.GA6258@Pilar>
[not found] ` <18379.18297.838050.536473@harpo.it.uu.se>
2008-03-03 1:48 ` Stefan Richter
2008-03-03 8:26 ` FUJITA Tomonori
2008-03-03 9:08 ` Stefan Richter
2008-03-03 9:45 ` Mikael Pettersson [this message]
2008-03-03 10:20 ` Mikael Pettersson
2008-03-03 10:29 ` Tejun Heo
2008-03-03 14:51 ` James Bottomley
2008-03-03 17:39 ` Stefan Richter
2008-03-03 18:00 ` Boris Petkov
2008-03-03 21:41 ` Stefan Richter
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=18379.51360.744676.894510@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=James.Bottomley@HansenPartnership.com \
--cc=crmafra2@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=htejun@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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