From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [3.8-{rc1,rc2}] ata1.00: failed to get Identify Device Data, Emask 0x1 Date: Wed, 16 Jan 2013 08:50:16 -0500 Message-ID: <50F6B018.2020800@pobox.com> References: <43EB3AB3EEFE8D43B525F4D2EAF507E107F4160E@SCYBEXDAG04.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-qc0-f173.google.com ([209.85.216.173]:43490 "EHLO mail-qc0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752688Ab3APNvW (ORCPT ); Wed, 16 Jan 2013 08:51:22 -0500 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: sedat.dilek@gmail.com Cc: "Huang, Shane" , "linux-ide@vger.kernel.org" , LKML , Aaron Lu , linux-next , Linus Torvalds On 01/16/2013 05:10 AM, Sedat Dilek wrote: > On Sat, Jan 5, 2013 at 3:20 AM, Huang, Shane 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