From: Johannes Berg <johannes@sipsolutions.net>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Aw: Re: Re: help for driver porting - missing member preset_chandef in struct wireless_dev
Date: Mon, 22 Aug 2022 21:19:38 +0200 [thread overview]
Message-ID: <7f9a39d1d1557afa09aa8b657a40f0c03e621cfa.camel@sipsolutions.net> (raw)
In-Reply-To: <trinity-94aeced0-7aab-4359-9c74-1616a17464bd-1661187572028@3c-app-gmx-bap06>
On Mon, 2022-08-22 at 18:59 +0200, Frank Wunderlich wrote:
> > Gesendet: Montag, 22. August 2022 um 18:43 Uhr
> > Von: "Johannes Berg" <johannes@sipsolutions.net>
>
> > On Mon, 2022-08-22 at 18:42 +0200, Frank Wunderlich wrote:
>
> > > thanks for response, commented out the use of the member and the
> > > wdev
> > > assignment as it was then unused
> > > can you tell me which api-call this should be?
> > > i just want to make sure this is really done as i up-ported the
> > > driver
> > > from 4.9, so if the api-call was introduced later it is maybe
> > > missing.
> >
> > No sorry, I don't know how the driver was/is using it, so I can't
> > tell
> > you how to replace it.
>
> can you give me possible calls (if there are multiple candidates)
> which may set the channel (without mesh)
> for me to check or maybe implement?
Well it seems to access it inside the start_ap callback, so it should
just check the configuration instea
prev parent reply other threads:[~2022-08-22 19:21 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
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 [this message]
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=7f9a39d1d1557afa09aa8b657a40f0c03e621cfa.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®