All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: sedat.dilek@gmail.com
Cc: "Huang, Shane" <Shane.Huang@amd.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Aaron Lu <aaron.lu@intel.com>,
	linux-next <linux-next@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
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	[thread overview]
Message-ID: <50F6B018.2020800@pobox.com> (raw)
In-Reply-To: <CA+icZUU7UmoYb5j7Pg57pMdgfw5GNA=M0aBuc5362o2t7Hqt3w@mail.gmail.com>

On 01/16/2013 05:10 AM, Sedat Dilek wrote:
> On Sat, Jan 5, 2013 at 3:20 AM, Huang, Shane <Shane.Huang@amd.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





      reply	other threads:[~2013-01-16 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 15:40 [3.8-{rc1,rc2}] ata1.00: failed to get Identify Device Data, Emask 0x1 Sedat Dilek
2013-01-04 15:59 ` Sedat Dilek
2013-01-04 16:27   ` Sedat Dilek
2013-01-05  2:20     ` Huang, Shane
2013-01-05  2:20       ` Huang, Shane
2013-01-05  8:49       ` Sedat Dilek
2013-01-16 10:10       ` Sedat Dilek
2013-01-16 13:50         ` 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=50F6B018.2020800@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Shane.Huang@amd.com \
    --cc=aaron.lu@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.