mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Frank Wunderlich <frank-w@public-files.de>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: help for driver porting - missing member preset_chandef in struct wireless_dev
Date: Mon, 22 Aug 2022 17:02:21 +0200	[thread overview]
Message-ID: <b081ef6eb978070740f31f48a1f4be1807f51168.camel@sipsolutions.net> (raw)
In-Reply-To: <trinity-de687d18-b2a2-4cde-9383-a4d6ddba6a77-1661177057496@3c-app-gmx-bap06>

On Mon, 2022-08-22 at 16:04 +0200, Frank Wunderlich wrote:
> hi,
> 
> i'm working on porting an old/huge wireless driver (mt6625l) [2] to linux 6.0 [1]
> 
> i hang on missing member preset_chandef in struct wireless_dev
> 
> 	struct wireless_dev *wdev = dev->ieee80211_ptr;
> 	struct cfg80211_chan_def *chandef = &wdev->preset_chandef;
> 
> it looks like this member is moved from the wdev into some mesh structure...my driver does not support mesh. any chance to fix this?
> 

Yes. Make sure the driver doesn't access it, it should get stuff through
other APIs.

johannes

  reply	other threads:[~2022-08-22 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 14:04 Frank Wunderlich
2022-08-22 15:02 ` Johannes Berg [this message]
2022-08-22 16:42   ` Aw: " Frank Wunderlich
2022-08-22 16:43     ` Johannes Berg
2022-08-22 16:59       ` Aw: " Frank Wunderlich
2022-08-22 19:19         ` Johannes Berg

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=b081ef6eb978070740f31f48a1f4be1807f51168.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=frank-w@public-files.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®