From: Jeff Garzik <jeff@garzik.org>
To: Mike Frysinger <vapier@gentoo.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: Tue, 14 Jul 2009 15:07:40 -0400 [thread overview]
Message-ID: <4A5CD77C.6070701@garzik.org> (raw)
In-Reply-To: <1247593187-26570-1-git-send-email-vapier@gentoo.org>
Mike Frysinger wrote:
> From: Sonic Zhang <sonic.zhang@analog.com>
>
> 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.
>
> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> Signed-off-by: Bryan Wu <cooloney@kernel.org>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> 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.
Jeff
next prev parent reply other threads:[~2009-07-14 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 17:39 [PATCH] libata: pata_bf54x: handle portmuxing of pins through GPIO PORTs Mike Frysinger
2009-07-14 19:07 ` Jeff Garzik [this message]
2009-07-14 23:01 ` Mike Frysinger
2009-12-21 14:21 ` Mike Frysinger
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=4A5CD77C.6070701@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sonic.zhang@analog.com \
--cc=vapier@gentoo.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