Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-next@vger.kernel.org, Jaswinder Singh <jaswinder@infradead.org>
Subject: linux-next: firmware tree build failure
Date: Tue, 22 Jul 2008 17:57:33 +1000	[thread overview]
Message-ID: <20080722175733.d436067a.sfr@canb.auug.org.au> (raw)

Hi Dave,

Today's linux-next build () failed like this:

drivers/scsi/qlogicpti.c:55:27: qlogicpti_asm.c: No such file or directory

I applied the following patch.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

>From c64dd1dfd140eb249684d85e927c7bae6f9d5328 Mon Sep 17 00:00:00 2001
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 22 Jul 2008 17:56:30 +1000
Subject: [PATCH] firmware: conversion fallout in qlogicpti.c

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/scsi/qlogicpti.c |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/drivers/scsi/qlogicpti.c b/drivers/scsi/qlogicpti.c
index 3e71436..17df63e 100644
--- a/drivers/scsi/qlogicpti.c
+++ b/drivers/scsi/qlogicpti.c
@@ -52,8 +52,6 @@
 
 #define DEFAULT_LOOP_COUNT	10000
 
-#include "qlogicpti_asm.c"
-
 static struct qlogicpti *qptichain = NULL;
 static DEFINE_SPINLOCK(qptichain_lock);
 
-- 
1.5.6.3

             reply	other threads:[~2008-07-22  7:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22  7:57 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-14  4:12 linux-next: firmware tree build failure Stephen Rothwell
2009-04-14 12:25 ` David Woodhouse
2009-04-15  1:56 ` David Woodhouse
2009-04-15  2:03   ` Stephen Rothwell
2008-07-22  8:04 Stephen Rothwell
2008-07-22  8:25 ` Jaswinder Singh
2008-07-22  7:47 Stephen Rothwell

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=20080722175733.d436067a.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dwmw2@infradead.org \
    --cc=jaswinder@infradead.org \
    --cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox