Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, jbenc@suse.cz, flamingice@sourmilk.net
Subject: patch mess
Date: Wed, 15 Aug 2007 13:02:22 +0200	[thread overview]
Message-ID: <1187175742.3998.25.camel@johannes.berg> (raw)

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

Hey,

It seems I've made quite a mess with patches interdependent on hostapd
and kernel patches.

Please drop all my patches for now.

Now that Jouni has merged a bunch of my patches I'll be going through
later today and will repost those that can be applied now because the
corresponding patches to hostapd have been merged, and I'll hold the
other ones. Then I'll rebase the other ones and post them as RFC again.

Review would still be appreciated :) I have, however, found a few minor
bugs in some patches that I've fixed too.

johannes

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

                 reply	other threads:[~2007-08-15 10:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1187175742.3998.25.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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