linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: LT-P <LT-P@lt-p.net>, Horms <horms@debian.org>,
	321442@bugs.debian.org, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: Bug#321442: kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c)
Date: Mon, 5 Sep 2005 14:42:43 +0200	[thread overview]
Message-ID: <58cb370e0509050542b512131@mail.gmail.com> (raw)
In-Reply-To: <C2F63384-9CC2-4979-956B-8CB5DA77F4AE@mac.com>

Should be fixed in 2.6.13.

On 8/16/05, Kyle Moffett <mrmacman_g4@mac.com> wrote:
> On Aug 13, 2005, at 18:54:30, LT-P wrote:
> > Le lun 08 aoû 2005 17:57:04 CEST, Horms <horms@debian.org> a écrit:
> >> Can you please enable BLK_DEV_IDEDMA_PCI and see if that resolves
> >> your
> >> problem. If it does, then the following patch should fix Kconfig
> >> so that BLK_DEV_IDEDMA_PCI needs to be enabled for BLK_DEV_IDE_PMAC
> >> to be enabled. It should patch cleanly against Debian's 2.6.8 and
> >> Linus' current Git tree.
> > It seems to solve the problem, thanks.
> > Sometimes, I feel like I am the only person in the world to compile
> > the kernel on
> > powerpc... :)
> 
> Actually, I ran into this same bug a day or so ago when updating to
> 2.6.13-rc6,
> it's just I noticed the error, fixed my config, then recompiled and
> forgot
> about it completely until now :-D.  Thanks for the bug report, though!
> 
> Cheers,
> Kyle Moffett

  reply	other threads:[~2005-09-05 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1E13vT-0008G7-R1@arda.LT-P.net>
2005-08-08  8:57 ` Bug#321442: kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c) Horms
2005-08-13 22:54   ` LT-P
2005-08-16 15:51     ` Erik Slagter
2005-08-16 18:11     ` Kyle Moffett
2005-09-05 12:42       ` Bartlomiej Zolnierkiewicz [this message]
2005-09-07  6:00         ` Horms

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=58cb370e0509050542b512131@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=321442@bugs.debian.org \
    --cc=LT-P@lt-p.net \
    --cc=horms@debian.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    /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).