All of lore.kernel.org
 help / color / mirror / Atom feed
From: frank.blaschka@de.ibm.com
To: jgarzik@pobox.com
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [patch 3/3] qeth: preallocated header account offset
Date: Fri, 15 Aug 2008 08:03:00 +0200	[thread overview]
Message-ID: <20080815060352.948003000@de.ibm.com> (raw)
In-Reply-To: 20080815060257.501264000@de.ibm.com

[-- Attachment #1: 602-qeth-prealloc-offset.diff --]
[-- Type: text/plain, Size: 819 bytes --]

From: Frank Blaschka <frank.blaschka@de.ibm.com>

When a preallocated header qdio buffer is filled we have to account
the offset for the data length.

Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
---

 drivers/s390/net/qeth_core_main.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: git_linus/drivers/s390/net/qeth_core_main.c
===================================================================
--- git_linus.orig/drivers/s390/net/qeth_core_main.c	2008-08-15 07:51:59.000000000 +0200
+++ git_linus/drivers/s390/net/qeth_core_main.c	2008-08-15 07:52:18.000000000 +0200
@@ -3024,7 +3024,7 @@
 	struct qdio_buffer *buffer, int is_tso, int *next_element_to_fill,
 	int offset)
 {
-	int length = skb->len;
+	int length = skb->len - offset;
 	int length_here;
 	int element;
 	char *data;

-- 

  parent reply	other threads:[~2008-08-15  6:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15  6:02 [patch 0/3] s390: qeth fixes for 2.6.27 frank.blaschka
2008-08-15  6:02 ` [patch 1/3] qeth: use -EOPNOTSUPP instead of -ENOTSUPP frank.blaschka
2008-08-15  6:02 ` [patch 2/3] qeth: l2 write unicast list to hardware frank.blaschka
2008-08-15  6:03 ` frank.blaschka [this message]
2008-08-27  9:56   ` [patch 3/3] qeth: preallocated header account offset 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=20080815060352.948003000@de.ibm.com \
    --to=frank.blaschka@de.ibm.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@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 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.