From: "Tomas Winkler" <tomasw@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: johannes@sipsolutions.net, ron.rindjunsky@intel.com,
linux-wireless@vger.kernel.org
Subject: Re: iwlwifi and tx info in skb->cb
Date: Fri, 9 May 2008 02:30:02 +0300 [thread overview]
Message-ID: <1ba2fa240805081630r3fdad2d7ya0e1e78fa69cb4ea@mail.gmail.com> (raw)
In-Reply-To: <20080508.162059.42870104.davem@davemloft.net>
On Fri, May 9, 2008 at 2:20 AM, David Miller <davem@davemloft.net> wrote:
> From: "Tomas Winkler" <tomasw@gmail.com>
> Date: Fri, 9 May 2008 02:16:14 +0300
>
>
> > On Fri, May 9, 2008 at 1:30 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
>
> > > Anyway, with the changes davem and I are making to actually save the
> > > *extra* copy we should be doing well. That's where you want to look for
> > > improvements.
> >
> > This is just for the bridging case, isn't it?
>
> No, all cases.
>
> We're repeating a lot of information for you, over and over
> again, it seems. Developers often find this frustrating,
> especially when they are trying to get their own work done.
>
Hey it's just second time and I explicitly wrote I will read the email
again, you choose to answer... anyway thanks for the answer :)
Tomas
prev parent reply other threads:[~2008-05-08 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 22:01 iwlwifi and tx info in skb->cb Johannes Berg
2008-05-07 23:29 ` Tomas Winkler
2008-05-07 23:30 ` Johannes Berg
2008-05-08 0:21 ` Tomas Winkler
2008-05-08 14:05 ` Johannes Berg
2008-05-08 22:07 ` Tomas Winkler
2008-05-08 22:10 ` Johannes Berg
2008-05-08 22:28 ` Tomas Winkler
2008-05-08 22:30 ` Johannes Berg
2008-05-08 23:16 ` Tomas Winkler
2008-05-08 23:17 ` Johannes Berg
2008-05-08 23:20 ` Johannes Berg
2008-05-08 23:20 ` David Miller
2008-05-08 23:30 ` Tomas Winkler [this message]
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=1ba2fa240805081630r3fdad2d7ya0e1e78fa69cb4ea@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ron.rindjunsky@intel.com \
/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