From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] ide-pmac: media-bay support fixes
Date: Tue, 24 Jun 2008 20:33:37 +1000 [thread overview]
Message-ID: <1214303617.8011.342.camel@pasglop> (raw)
In-Reply-To: <200806232345.07621.bzolnier@gmail.com>
> I (naively?) hope that you are using ide-pmac as a base (the driver looks
> like a normal host driver now) and going to make the final API switch after
> hardware specific changes are complete (so we will be able to use git-bisect
> instead of guesswork combined with voodoo dance when dealing with potential
> regressions :-).
I intend to yes :-) Along with my WIP pata_macio of course but I don't
like leaving a driver broken and/or non bisectable, believe me.
> You may want to look at ACPI hotplug dock handling for inspiration
> (if you haven't already).
Thanks, I will. I've been busy with all sorts of other things so no, I
haven't looked yet, and it's a bit less urgent, but thanks for the
pointer,
> There is no longer any hackery on IDE core code side in 2.6.26, there are
> just two nice methods: ide_port_unregister_devices() and ide_scan_port().
Sure but the fact that mediabay calls them directly makes it painful to
deal with 2 drivers, one using drivers/ide and one libata. So I want to
turn that into a notification into the low level driver so it does what
is appropriate.
> Therefore I would prefer to also update ide-pmac for new methods and just
> add what is needed (if any) to IDE core code.
Sure. I don't think I will need to change any of the core.
> [ Please keep me in loop on these mediabay changes. ]
I'll let you know when I get something done.
Cheers,
Ben.
next prev parent reply other threads:[~2008-06-24 10:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 19:24 [PATCH 1/4] ide-pmac: media-bay support fixes Bartlomiej Zolnierkiewicz
2008-06-17 3:39 ` Benjamin Herrenschmidt
2008-06-17 3:49 ` Benjamin Herrenschmidt
2008-06-17 9:41 ` Bartlomiej Zolnierkiewicz
2008-06-17 9:58 ` Bartlomiej Zolnierkiewicz
2008-06-23 5:35 ` Benjamin Herrenschmidt
2008-06-23 5:54 ` Benjamin Herrenschmidt
2008-06-23 6:41 ` Benjamin Herrenschmidt
2008-06-23 10:47 ` Benjamin Herrenschmidt
2008-06-23 21:45 ` Bartlomiej Zolnierkiewicz
2008-06-24 10:33 ` Benjamin Herrenschmidt [this message]
2008-06-23 21:00 ` Bartlomiej Zolnierkiewicz
2008-06-24 10:34 ` Benjamin Herrenschmidt
2008-06-24 18:51 ` Bartlomiej Zolnierkiewicz
2008-06-24 18:55 ` Bartlomiej Zolnierkiewicz
2008-06-26 4:54 ` Benjamin Herrenschmidt
2008-06-26 8:51 ` Bartlomiej Zolnierkiewicz
2008-06-26 9:01 ` Benjamin Herrenschmidt
2008-06-26 9:40 ` Bartlomiej Zolnierkiewicz
2008-07-03 5:33 ` Benjamin Herrenschmidt
2008-07-03 6:47 ` Benjamin Herrenschmidt
2008-07-03 7:33 ` Benjamin Herrenschmidt
2008-07-05 15:56 ` Bartlomiej Zolnierkiewicz
2008-07-05 22:25 ` Benjamin Herrenschmidt
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=1214303617.8011.342.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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).