public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: bunk@fs.tum.de
Cc: jgarzik@pobox.com, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org, trivial@rustcorp.com.au
Subject: Re: [2.5 patch] ULL postfixes for tg3.c
Date: Tue, 24 Jun 2003 13:12:28 -0700 (PDT)	[thread overview]
Message-ID: <20030624.131228.78737223.davem@redhat.com> (raw)
In-Reply-To: <20030624174811.GW3710@fs.tum.de>


I'll apply this, the INT64_MAX or whatever ideas are just
stupid.  We're saying what "bits" the device supports when
it does DMA, so we should pass in a "bit" mask.

  reply	other threads:[~2003-06-24 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 17:48 [2.5 patch] ULL postfixes for tg3.c Adrian Bunk
2003-06-24 20:12 ` David S. Miller [this message]
2003-06-24 20:32   ` Arjan van de Ven
2003-06-24 20:34   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2003-06-24 18:00 Eble, Dan
2003-06-24 18:20 ` Adrian Bunk

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=20030624.131228.78737223.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=bunk@fs.tum.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=trivial@rustcorp.com.au \
    /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