All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	Tomas Winkler <tomasw@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Stefano Brivio <stefano.brivio@polimi.it>
Subject: Re: should we revert the cfg80211 API patches?
Date: Wed, 30 Jan 2008 17:13:15 +0100	[thread overview]
Message-ID: <200801301713.15962.mb@bu3sch.de> (raw)
In-Reply-To: <1201708352.4149.21.camel@johannes.berg>

On Wednesday 30 January 2008 16:52:31 Johannes Berg wrote:
> John,
> 
> It appears that there's more trouble caused by my cfg80211 band API
> patch than people are willing to put up with. Tomas has already asked
> for it to be reverted, and neither Michael (Buesch) nor Stefano want to
> maintain two driver branches (one "stable" 2.6.25 branch and one
> "development" "for the future" branch).

No wait. I always supported that and will support that in the future.

But the problem I see with not merging this patch is that I think
it is _just_ wasted time in the end. If we simply merge it now we
can easily fix bugs in the huge merge window.
If we don't merge it, we are creating a branch of the driver. So
far no problem, really. But, if a bug appears that has to be fixed
differently for the old API and the new API, I'm not going to make
two patches. Simply because this could have beed avoided as a whole
by simply merging that patch _now_. I wish I had unlimited time to
port patches back. But I simply don't. So I am going to port patches
back that are needed, but not those for which we artificially created
the problems.

To say it again. I do support the concept of "stable" and "development"
branches. But I do not support artificial branching that is not needed
at all and can easily be avoided by simply applying that patch.

Just my 2ct.

-- 
Greetings Michael.

  reply	other threads:[~2008-01-30 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 15:52 should we revert the cfg80211 API patches? Johannes Berg
2008-01-30 16:13 ` Michael Buesch [this message]
2008-01-30 16:16 ` Jory A. Pratt
2008-01-30 16:25   ` Tomas Winkler
2008-01-31 15:13     ` Luis R. Rodriguez

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=200801301713.15962.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=stefano.brivio@polimi.it \
    --cc=tomasw@gmail.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 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.