linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Maya Erez <merez@codeaurora.org>
Cc: Lior David <liord@codeaurora.org>,
	linux-wireless@vger.kernel.org, wil6210@qti.qualcomm.com,
	Maya Erez <merez@codeaurora.org>
Subject: Re: [1/8] wil6210: add wil6210_vif structure for per-VIF data
Date: Mon, 26 Feb 2018 16:24:45 +0000 (UTC)	[thread overview]
Message-ID: <20180226162447.6193E60F72@smtp.codeaurora.org> (raw)
In-Reply-To: <1518768283-2318-2-git-send-email-merez@codeaurora.org>

Maya Erez <merez@codeaurora.org> wrote:

> From: Lior David <liord@codeaurora.org>
> 
> For supporting multiple virtual interfaces in the future,
> introduce a wil6210_vif structure which will hold per-VIF
> data. Change the module initialization so wil6210_vif will
> be part of net_device structure, and wireless_dev will be
> embedded inside the wil6210_vif structure. This will allow
> us to find the appropriate wil6210_vif structure when we
> only have access to wireless_dev or net_device.
> 
> Signed-off-by: Lior David <liord@codeaurora.org>
> Signed-off-by: Maya Erez <merez@codeaurora.org>

Failed to apply:

error: patch failed: drivers/net/wireless/ath/wil6210/cfg80211.c:1606
error: drivers/net/wireless/ath/wil6210/cfg80211.c: patch does not apply
stg import: Diff does not apply cleanly

8 patches set to Changes Requested.

10224163 [1/8] wil6210: add wil6210_vif structure for per-VIF data
10224157 [2/8] wil6210: support concurrency record in FW file
10224159 [3/8] wil6210: infrastructure for multiple virtual interfaces
10224161 [4/8] wil6210: add support for adding and removing virtual interfaces
10224155 [5/8] wil6210: multiple VIFs support for start/stop AP
10224151 [6/8] wil6210: rename p2p_wdev_mutex to vif_mutex
10224153 [7/8] wil6210: multiple VIFs support for connections and data path
10224149 [8/8] wil6210: add debugfs 'mids' file

-- 
https://patchwork.kernel.org/patch/10224163/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2018-02-26 16:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16  8:04 [PATCH 0/8] wil6210 patches Maya Erez
2018-02-16  8:04 ` [PATCH 1/8] wil6210: add wil6210_vif structure for per-VIF data Maya Erez
2018-02-26 16:24   ` Kalle Valo [this message]
2018-02-16  8:04 ` [PATCH 2/8] wil6210: support concurrency record in FW file Maya Erez
2018-02-16  8:04 ` [PATCH 3/8] wil6210: infrastructure for multiple virtual interfaces Maya Erez
2018-02-16  8:04 ` [PATCH 4/8] wil6210: add support for adding and removing " Maya Erez
2018-02-16  8:04 ` [PATCH 5/8] wil6210: multiple VIFs support for start/stop AP Maya Erez
2018-02-16  8:04 ` [PATCH 6/8] wil6210: rename p2p_wdev_mutex to vif_mutex Maya Erez
2018-02-16  8:04 ` [PATCH 7/8] wil6210: multiple VIFs support for connections and data path Maya Erez
2018-02-16  8:04 ` [PATCH 8/8] wil6210: add debugfs 'mids' file Maya Erez

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=20180226162447.6193E60F72@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=liord@codeaurora.org \
    --cc=merez@codeaurora.org \
    --cc=wil6210@qti.qualcomm.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;
as well as URLs for NNTP newsgroup(s).