From: Mike Frysinger <vapier.adi@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Sonic Zhang <sonic.zhang@analog.com>,
Bryan Wu <cooloney@kernel.org>
Subject: Re: [PATCH] libata: pata_bf54x: handle portmuxing of pins through GPIO PORTs
Date: Mon, 21 Dec 2009 09:21:03 -0500 [thread overview]
Message-ID: <8bd0f97a0912210621g19535a03q38b8b67c01df6a75@mail.gmail.com> (raw)
In-Reply-To: <4A5CD77C.6070701@garzik.org>
On Tue, Jul 14, 2009 at 14:07, Jeff Garzik wrote:
> Mike Frysinger wrote:
>> By default, the PATA pins are routed to the async address lines in which
>> case, no peripheral muxing needs to be done. However, if the pins get
>> routed through the GPIO PORTs pins, we need to make sure to request them
>> so that the muxing is properly set up.
>> ---
>> Andrew: could you pick this up ? it was posted over a month ago to the
>> Linux/IDE list w/no feedback.
>
> Although it is disappointing that your patch was missed -- our apologies --
> I don't think the best response was to elide linux-ide and the libata
> maintainer, in favor of a higher noise list. :)
>
> I have the patch queued, now.
so it's been 8 months since it was posted, 6 months since it was
queued, and multiple libata merges have been made, but this patch has
yet to make it into mainline ...
-mike
next prev parent reply other threads:[~2009-12-21 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 17:39 Mike Frysinger
2009-07-14 19:07 ` Jeff Garzik
2009-07-14 23:01 ` Mike Frysinger
2009-12-21 14:21 ` Mike Frysinger [this message]
2009-12-21 18:54 ` Alan Cox
2009-12-21 18:58 ` Jeff Garzik
2009-12-21 18:57 ` Jeff Garzik
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=8bd0f97a0912210621g19535a03q38b8b67c01df6a75@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cooloney@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sonic.zhang@analog.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
all inboxes | Powered by JetHome®