From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: netdev <netdev@vger.kernel.org>, linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211-next next-2020-02-24
Date: Mon, 24 Feb 2020 20:34:06 +0100 [thread overview]
Message-ID: <f9530f24f221e2a5c2fe5dc20632b83ecbd87c86.camel@sipsolutions.net> (raw)
In-Reply-To: <BCCC37CB-FA6D-433C-B772-EC46EF734FED@holtmann.org>
On Mon, 2020-02-24 at 20:33 +0100, Marcel Holtmann wrote:
>
> so I am bit concerned if these reverts are pushed so quickly without
> allowing ample time to discuss or review them on the mailing list. I
> for one, don’t agree with the assessment made to justify these
> reverts.
No no, you have it the wrong way around.
The reverts are pushed out quickly so that we _have_ time to argue and
come to an agreement on this, because otherwise we're locked in to the
API if we don't act ...
johannes
next prev parent reply other threads:[~2020-02-24 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 18:34 pull-request: mac80211-next next-2020-02-24 Johannes Berg
2020-02-24 19:33 ` Marcel Holtmann
2020-02-24 19:34 ` Johannes Berg [this message]
2020-02-24 23:42 ` David Miller
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=f9530f24f221e2a5c2fe5dc20632b83ecbd87c86.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@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