linux-kernel - Re: [3.8-{rc1,rc2}] ata1.00: failed to get Identify Device Data, Emask 0x1

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]

Date:	Wed, 16 Jan 2013 08:50:16 -0500
From:	Jeff Garzik <jgarzik@...ox.com>
To:	sedat.dilek@...il.com
CC:	"Huang, Shane" <Shane.Huang@....com>,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Aaron Lu <aaron.lu@...el.com>,
	linux-next <linux-next@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [3.8-{rc1,rc2}] ata1.00: failed to get Identify Device Data,
 Emask 0x1

On 01/16/2013 05:10 AM, Sedat Dilek wrote:
> On Sat, Jan 5, 2013 at 3:20 AM, Huang, Shane <Shane.Huang@....com> wrote:
>>> OK, I see the patch I mentioned to fix the problem was later reverted [1].
>>> The real fix is "libata: replace sata_settings with devslp_timing" [2].
>>
>> Yes, please use [2] which can also be found in kernel bugzilla #51881
>> and is pending on Jeff's acceptance. Sorry for the trouble to you guys.
>>
>
> [ CCing Linus ]
>
> Thanks for taking care (my latest experiences on LKML/linux-next tell
> me even this is no more the fact!)!
>
> Your patch finally hit Linux-Next (next-20130116) and IIRC it is also
> marked for previous Linux-kernel releases (CC -stable).
> I have tested your patch as said also against Linux v3.8-rcX.
>
> Unfortunately, the applied patch in Linux-Next does not contain any of
> my desired Reported-by/Tested-by.
> This makes me a bit unhappy, but I do NOT insist on it.
>
> Mr. Torvalds himself pointed several times to all maintainers to
> honour people - even they report and ideally report-and-test!
>
> I am doing all my testings in my free-time and I am not paid for it.
> I am raping my hardware here!
> I can't do more than that!

We definitely appreciate that.  The patch in question actually went into 
the git repository before your report was received.  You did not see it 
in linux-next until my local git repository was pushed out to kernel.org 
(and thus automatically included in linux-next).

	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/