DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type:content-transfer-encoding;
        b=H62oaTyUWWd3Oy1CNsl2IZi/yiKiqLUQFSP8AxFOb21kAOoeKiJoJ7MHRe6zFtu6LG
         ic5cGROGpGmMSG4q4kVTlQkoK/7C6GYs7Ml/dfJ+KIK7DinwEiEHr6FyyeufbmhIu3e2
         Glc6G5poIc8bLT0ZJmPxTPRr6u+edfQSiZNaM=
MIME-Version: 1.0
In-Reply-To: <4A5CD77C.6070701@garzik.org>
References: <1247593187-26570-1-git-send-email-vapier@gentoo.org> 
	<4A5CD77C.6070701@garzik.org>
From: Mike Frysinger <vapier.adi@gmail.com>
Date: Mon, 21 Dec 2009 09:21:03 -0500
Message-ID: <8bd0f97a0912210621g19535a03q38b8b67c01df6a75@mail.gmail.com>
Subject: Re: [PATCH] libata: pata_bf54x: handle portmuxing of pins through 
	GPIO PORTs
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>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1117
Lines: 25

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/