public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>,
	James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: mm snapshot broken-out-2007-01-26-00-36.tar.gz uploaded
Date: Sat, 27 Jan 2007 18:20:59 +0100	[thread overview]
Message-ID: <45BB89FB.5000104@googlemail.com> (raw)
In-Reply-To: <200701260837.l0Q8blBr011622@shell0.pdx.osdl.net>

akpm@osdl.org napisał(a):
> The mm snapshot broken-out-2007-01-26-00-36.tar.gz has been uploaded to
> 
>    ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-01-26-00-36.tar.gz
> 

git-scsi-misc.patch typo fix.

drivers/scsi/NCR_D700.c: In function ‘NCR_D700_probe_one’:
drivers/scsi/NCR_D700.c:203: error: ‘struct NCR_700_Host_Parameters’ has no member named ‘busrt_length’
make[2]: *** [drivers/scsi/NCR_D700.o] Błąd 1
make[1]: *** [drivers/scsi] Błąd 2
make: *** [drivers] Błąd 2

Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)

Signed-off-by: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>

--- linux-work-clean/drivers/scsi/NCR_D700.c	2007-01-26 16:47:36.000000000 +0100
+++ linux-work/drivers/scsi/NCR_D700.c	2007-01-27 18:13:42.000000000 +0100
@@ -200,7 +200,7 @@ NCR_D700_probe_one(struct NCR_D700_priva
 	hostdata->base = ioport_map(region, 64);
 	hostdata->differential = (((1<<siop) & differential) != 0);
 	hostdata->clock = NCR_D700_CLOCK_MHZ;
-	hostdata->busrt_length = 8;
+	hostdata->burst_length = 8;

 	/* and register the siop */
 	host = NCR_700_detect(&NCR_D700_driver_template, hostdata, p->dev);

  parent reply	other threads:[~2007-01-27 17:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200701260837.l0Q8blBr011622@shell0.pdx.osdl.net>
2007-01-26 15:04 ` mm snapshot broken-out-2007-01-26-00-36.tar.gz uploaded Michal Piotrowski
2007-01-26 15:33   ` Serge E. Hallyn
2007-01-26 15:38     ` Serge E. Hallyn
2007-01-26 16:06       ` Michal Piotrowski
2007-01-26 16:37 ` Michal Piotrowski
2007-01-26 16:46 ` Michal Piotrowski
2007-01-26 16:57 ` Michal Piotrowski
2007-01-26 17:29 ` Michal Piotrowski
2007-01-26 18:14   ` Serge E. Hallyn
2007-01-26 18:22     ` Michal Piotrowski
2007-01-26 18:58       ` Serge E. Hallyn
2007-01-26 17:48 ` Michal Piotrowski
2007-01-26 18:04 ` Michal Piotrowski
     [not found]   ` <6bffcb0e0701261008u2fd5a7d9va16d7fd9f250e14b@mail.gmail.com>
2007-01-26 18:38     ` Christoph Lameter
2007-01-26 18:43       ` Pavel Machek
2007-01-26 18:45       ` Michal Piotrowski
2007-01-26 19:07         ` Christoph Lameter
2007-01-26 19:20           ` Michal Piotrowski
2007-01-26 19:45 ` Michal Piotrowski
     [not found]   ` <6bffcb0e0701261523j3a84a357lad93260b5865c99d@mail.gmail.com>
2007-01-27  0:33     ` Andrew Morton
2007-01-27  0:41       ` Michal Piotrowski
2007-01-27  0:29 ` Michal Piotrowski
2007-01-27 15:05 ` Michal Piotrowski
2007-01-27 20:38   ` Herbert Xu
2007-01-27 16:03 ` Michal Piotrowski
2007-01-30  1:05   ` Tejun Heo
2007-01-27 16:14 ` Michal Piotrowski
2007-01-27 17:20 ` Michal Piotrowski [this message]
     [not found] ` <6bffcb0e0701270837i1ec40560l6e61e8876177e9da@mail.gmail.com>
2007-01-27 21:29   ` Tilman Schmidt
2007-01-27 21:41     ` Andrew Morton
2007-01-27 22:12       ` Michal Piotrowski
2007-01-27 23:25       ` Tilman Schmidt
2007-01-27 23:27         ` Michal Piotrowski
2007-01-28  2:41       ` Valdis.Kletnieks
2007-01-28  3:37         ` Michal Piotrowski
2007-01-29  2:49         ` Valdis.Kletnieks
2007-01-29  6:08           ` Eric W. Biederman
2007-01-29  6:45             ` Valdis.Kletnieks
2007-01-29  8:24               ` Eric W. Biederman
2007-01-29  2:58         ` Valdis.Kletnieks
2007-01-29  5:14           ` Randy Dunlap
2007-01-29  5:46           ` Valdis.Kletnieks

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=45BB89FB.5000104@googlemail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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