linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 015-mac80211-tx-info-skb-cb.patch
Date: Thu, 08 May 2008 17:28:29 +0200	[thread overview]
Message-ID: <1210260509.3547.62.camel@johannes.berg> (raw)
In-Reply-To: <200805081734.23354.IvDoorn@gmail.com> (sfid-20080508_172446_517725_0910B37D)

[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]

On Thu, 2008-05-08 at 17:34 +0200, Ivo van Doorn wrote:
> On Thursday 08 May 2008, Johannes Berg wrote:
> > 
> > > > Right :) I'm pretty much done with the skb->cb conversion too except for
> > > > ath5k (nick) and rt2x00 (you)
> > > 
> > > I'm going to rebase rt2x00.git this weekend to update from wireless-testing,
> > > since the skb->cb patches now depends on HW crypto which is not ready
> > > for upstream yet, I am going to reverse the patch order so the skb->cb patches
> > > and some other updates can go upstream more easily.
> > 
> > Cool, thanks. If you have a single patch that can pretty much go into
> > wireless-testing you can send it to me and I'll roll it into my patch.
> 
> Well at the moment I have it split into 2 patches, one that is only
> preperation work by splitting a particular function to guarentee the skb->cb
> rules are being followed. And the second patch is the actual conversion.
> Those 2 can easily be merged into a single patch which you can roll into your
> patch.

Whatever you like better. Maybe it's easier to follow the code/patch
flow if your preparation patch goes in first on its own?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2008-05-08 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 13:03 015-mac80211-tx-info-skb-cb.patch Ivo van Doorn
2008-05-08 14:43 ` 015-mac80211-tx-info-skb-cb.patch Johannes Berg
2008-05-08 14:57   ` 015-mac80211-tx-info-skb-cb.patch Ivo van Doorn
2008-05-08 14:50     ` 015-mac80211-tx-info-skb-cb.patch Johannes Berg
2008-05-08 15:10       ` 015-mac80211-tx-info-skb-cb.patch Ivo van Doorn
2008-05-08 15:05         ` 015-mac80211-tx-info-skb-cb.patch Johannes Berg
2008-05-08 15:34           ` 015-mac80211-tx-info-skb-cb.patch Ivo van Doorn
2008-05-08 15:28             ` Johannes Berg [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=1210260509.3547.62.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).