All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
	Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>,
	Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
	John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Subject: Re: [PATCH] bcm43xx-softmac: optimization of DMA bitfields.]
Date: Wed, 16 Aug 2006 11:02:00 -0500	[thread overview]
Message-ID: <44E34178.8040303@lwfinger.net> (raw)
In-Reply-To: <200608161757.37807.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>

Michael Buesch wrote:
> On Wednesday 16 August 2006 17:52, Larry Finger wrote:
>> Johannes Berg wrote:
>>> On Wed, 2006-08-16 at 10:36 -0500, Larry Finger wrote:
>>>> +	/* Boolean. Is this a TX ring? */
>>>> +	u8 tx
>>>> +	/* Boolean. 64bit DMA if true, 32bit DMA otherwise. */
>>>> +	u8 dma64;
>>> does that compile?
>>>
>>> johannes
>>>
>> Yes, it did here. Did you have a problem?
> 
> You removed a ; by mistake.
> Look, it's there in my original patch (which was compile tested).
> 
I saw that just after I sent the response to Johannes. I don't know
how that ; got deleted, but a revised version will be on to John soon.

Larry

  parent reply	other threads:[~2006-08-16 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 15:36 [PATCH] bcm43xx-softmac: optimization of DMA bitfields.] Larry Finger
2006-08-16 15:42 ` Johannes Berg
2006-08-16 15:52   ` Larry Finger
     [not found]     ` <44E33F3E.2000509-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-08-16 15:57       ` Michael Buesch
     [not found]         ` <200608161757.37807.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-08-16 16:02           ` Larry Finger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-16 16:05 Larry Finger

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=44E34178.8040303@lwfinger.net \
    --to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
    --cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.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.