mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Wolfgang Pfeiffer <roto@gmx.net>,
	Ben Collins <bcollins@ubuntu.com>, Andrew Morton <akpm@osdl.org>
Subject: [PATCH 1/2] ieee1394: ohci1394: fix endianess bug in debug message
Date: Fri, 8 Sep 2006 01:57:09 +0200 (CEST)	[thread overview]
Message-ID: <tkrat.e527c910c204d2e6@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.e9e9aee005df0fb6@s5r6.in-berlin.de>

The transaction labels were misprinted int the debug printk "Packet
received from node..." due two byte-swapping once too often.  Affected
were big endian machines, except UniNorth based ones.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
Index: linux/drivers/ieee1394/ohci1394.c
===================================================================
--- linux.orig/drivers/ieee1394/ohci1394.c	2006-09-06 23:50:53.000000000 +0200
+++ linux/drivers/ieee1394/ohci1394.c	2006-09-07 15:48:15.000000000 +0200
@@ -2743,7 +2743,7 @@ static void dma_rcv_tasklet (unsigned lo
 				(cond_le32_to_cpu(d->spb[length/4-1], ohci->no_swap_incoming)>>16)&0x1f,
 				(cond_le32_to_cpu(d->spb[length/4-1], ohci->no_swap_incoming)>>21)&0x3,
 				tcode, length, d->ctx,
-				(cond_le32_to_cpu(d->spb[0], ohci->no_swap_incoming)>>10)&0x3f);
+				(d->spb[0]>>10)&0x3f);
 
 			ack = (((cond_le32_to_cpu(d->spb[length/4-1], ohci->no_swap_incoming)>>16)&0x1f)
 				== 0x11) ? 1 : 0;



  reply	other threads:[~2006-09-07 23:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 23:55 [PATCH 0/2] ieee1394: ohci1394: endianess bug in verbose debug log Stefan Richter
2006-09-07 23:57 ` Stefan Richter [this message]
2006-09-07 23:59 ` [PATCH 2/2] ieee1394: ohci1394: more obvious endianess handling Stefan Richter
2006-09-10 13:00 ` [PATCH 0/2] ieee1394: ohci1394: endianess bug in verbose debug log Wolfgang Pfeiffer

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=tkrat.e527c910c204d2e6@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@osdl.org \
    --cc=bcollins@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=roto@gmx.net \
    /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

all inboxes | Powered by JetHome®