linux-kernel - Re: [PATCH] libata: pata_bf54x: handle portmuxing of pins through GPIO PORTs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4B2FC54D.1070000@garzik.org>
Date:	Mon, 21 Dec 2009 13:58:21 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Mike Frysinger <vapier.adi@...il.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Sonic Zhang <sonic.zhang@...log.com>,
	Bryan Wu <cooloney@...nel.org>
Subject: Re: [PATCH] libata: pata_bf54x: handle portmuxing of pins through
 	GPIO PORTs

On 12/21/2009 09:21 AM, Mike Frysinger wrote:
> 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 ...

No idea how it got lost :(   Just sent a pull request to Linus with this 
in it.

	Jeff




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