linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
Cc: Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Peer Chen <pchen@nvidia.com>
Subject: Re: [PATCH] ahci: retry enabling AHCI a few times before spitting out WARN_ON()
Date: Thu, 24 Apr 2008 13:01:13 +0900	[thread overview]
Message-ID: <48100609.6000508@gmail.com> (raw)
In-Reply-To: <200804240557.42428.volker.armin.hemmann@tu-clausthal.de>

Volker Armin Hemmann wrote:
> On Donnerstag, 24. April 2008, Tejun Heo wrote:
>> Volker Armin Hemmann wrote:
>>> On Donnerstag, 24. April 2008, Tejun Heo wrote:
>>>> Ah.. right.  The patch is for libata-dev#upstream branch which contains
>>>> ahci_enable_ahci() refactoring change.  You'll need to get the latest
>>>> linux-2.6 git tree which contains it.
>>> which isn't -git4
>>>
>>> *sigh*
>>>
>>> then I did:
>>> git clone
>>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>>> Initialized empty Git repository in /usr/src/linux-2.6/.git/
>>> remote: Counting objects: 761806, done.
>>> remote: Compressing objects: 100% (130538/130538), done.
>>> remote: Total 761806 (delta 633235), reused 758782 (delta 630257)
>>> Receiving objects: 100% (761806/761806), 179.18 MiB | 10975 KiB/s, done.
>>> Resolving deltas: 100% (633235/633235), done.
>>> Checking out files: 100% (23886/23886), done.
>>>
>>> cd linux-2.6
>>> patch -p1 < ../ahci.patch
>>> patching file drivers/ata/ahci.c
>>> Hunk #1 FAILED at 556.
>>> 1 out of 1 hunk FAILED -- saving rejects to file drivers/ata/ahci.c.rej
>> If you can git, just do the following...
>>
>> $ git fetch
>> git://git.kernel.org//pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>> upstream:upstream $ git checkout -f upstream
>> $ patch -p1 < ahci.patch
>>
>> Thanks.
> 
> that did not work:
> 
> git fetch 
> git://git.kernel.org//pub/scm/linux/kernel/git/jgarzik/libata-dev.git 
> upstream:upstream

Heh... it should have been git://git.kernel.org/pub/scm... w/o the 
double slashes.  Sorry.

-- 
tejun

  reply	other threads:[~2008-04-24  4:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 11:52 [PATCH] ahci: retry enabling AHCI a few times before spitting out WARN_ON() Tejun Heo
2008-04-24  0:24 ` Volker Armin Hemmann
2008-04-24  1:34   ` Tejun Heo
2008-04-24  1:51     ` Volker Armin Hemmann
2008-04-24  2:57       ` Tejun Heo
2008-04-24  3:28         ` Volker Armin Hemmann
2008-04-24  3:36           ` Tejun Heo
2008-04-24  3:57             ` Volker Armin Hemmann
2008-04-24  4:01               ` Tejun Heo [this message]
2008-04-24  4:15                 ` Volker Armin Hemmann
2008-04-24  4:20                   ` Tejun Heo
2008-04-24  4:32                     ` Volker Armin Hemmann
2008-04-25  0:17                     ` Volker Armin Hemmann
2008-04-25  0:44                       ` Tejun Heo
2008-04-25  1:17                         ` Volker Armin Hemmann
2008-04-25  1:59                           ` Tejun Heo
2008-04-25  2:40                             ` Volker Armin Hemmann
2008-04-25  4:47 ` Jeff Garzik

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=48100609.6000508@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=pchen@nvidia.com \
    --cc=volker.armin.hemmann@tu-clausthal.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).