public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mike Frysinger <vapier@gentoo.org>,
	Linus Torvalds <torvalds@linux-foundation.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 13:57:43 -0500	[thread overview]
Message-ID: <4B2FC527.2010301@garzik.org> (raw)
In-Reply-To: <1247593187-26570-1-git-send-email-vapier@gentoo.org>

On 07/14/2009 01:39 PM, 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.
>
>   drivers/ata/pata_bf54x.c |   19 +++++++++++++++++++
>   1 files changed, 19 insertions(+), 0 deletions(-)


Added to the tip of libata-dev...

Linus, if you pull

master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git 
upstream-linus

then you will receive the previous pull (two pata_cmd64x fixes), plus 
the above fix to pata_bf54x.


      parent reply	other threads:[~2009-12-21 18:57 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
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 [this message]

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=4B2FC527.2010301@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=torvalds@linux-foundation.org \
    --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