From: Johannes Berg <johannes@sipsolutions.net>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Andrew Lunn <andrew@lunn.ch>,
Simon Dietz <simon.dietz@plantwatch.de>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net,
dietz23838@hs-ansbach.de, edumazet@google.com,
kuniyu@google.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: short description of GeoNetworking
Date: Sat, 25 Jul 2026 10:55:28 +0200 [thread overview]
Message-ID: <9c4227befb03ff30c087a9d192bb3da879adc823.camel@sipsolutions.net> (raw)
In-Reply-To: <0f5b698c-6edf-4d8d-bc8b-a77af4be42dc@oss.qualcomm.com>
On Fri, 2026-07-24 at 18:26 -0700, Jeff Johnson wrote:
> On 7/23/2026 5:37 AM, Johannes Berg wrote:
> > A bigger issue with this might be that it's clearly a small piece of a
> > large overall puzzle - Simon, you mentioned a modified driver somewhere
> > I think (can't find that mention right now), which may be using the OCB
> > support in the stack, perhaps, but also isn't upstream.
>
> The ath9k driver is patched per the information at:
> https://gitlab.com/hpi-potsdam/osm/g5-on-linux/11p-on-linux
That's a far smaller patch than I expected :)
johannes
prev parent reply other threads:[~2026-07-25 8:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 21:00 [RFC PATCH net-next v0.1 0/1] add GeoNetworking protocol Simon Dietz
2026-07-18 21:00 ` [RFC PATCH net-next v0.1 1/1] net: " Simon Dietz
2026-07-19 17:16 ` Andrew Lunn
2026-07-23 18:54 ` Simon Dietz
2026-07-19 17:28 ` Andrew Lunn
2026-07-19 23:33 ` Andrew Lunn
2026-07-23 17:12 ` Simon Dietz
2026-07-23 17:54 ` Andrew Lunn
2026-07-23 18:24 ` Simon Dietz
2026-07-23 17:43 ` short description of GeoNetworking Simon Dietz
2026-07-23 18:05 ` Andrew Lunn
2026-07-23 18:38 ` [RFC PATCH net-next v0.1 1/1] net: add GeoNetworking protocol Simon Dietz
2026-07-19 16:21 ` [RFC PATCH net-next v0.1 0/1] " Andrew Lunn
2026-07-20 18:36 ` short description of GeoNetworking Simon Dietz
2026-07-20 20:16 ` Andrew Lunn
2026-07-22 21:34 ` Simon Dietz
2026-07-23 0:30 ` Andrew Lunn
2026-07-23 12:37 ` Johannes Berg
2026-07-25 1:26 ` Jeff Johnson
2026-07-25 8:55 ` 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=9c4227befb03ff30c087a9d192bb3da879adc823.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dietz23838@hs-ansbach.de \
--cc=edumazet@google.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=kuniyu@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon.dietz@plantwatch.de \
/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