linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Grzegorz Bajorski <grzegorz.bajorski@tieto.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: allow drivers to report (non-)monitor frames
Date: Mon, 30 Nov 2015 14:14:31 +0100	[thread overview]
Message-ID: <1448889271.3957.2.camel@sipsolutions.net> (raw)
In-Reply-To: <1448888094-2707-1-git-send-email-grzegorz.bajorski@tieto.com> (sfid-20151130_135514_150954_6D7D0B87)

On Mon, 2015-11-30 at 13:54 +0100, Grzegorz Bajorski wrote:
> This allows drivers to tell mac80211 whether given
> frame is to be processed regularly but skip
> monitor interface delivery or vice versa.
> 
Can you give an example, and perhaps a corresponding driver patch?

johannes

  reply	other threads:[~2015-11-30 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 12:54 [PATCH] mac80211: allow drivers to report (non-)monitor frames Grzegorz Bajorski
2015-11-30 13:14 ` Johannes Berg [this message]
2015-12-01  8:07   ` Grzegorz Bajorski
2015-12-01  8:32     ` Johannes Berg
2015-12-11 13:39 ` [PATCHv2] " Grzegorz Bajorski

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=1448889271.3957.2.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=grzegorz.bajorski@tieto.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).