B.A.T.M.A.N Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH RFC batadv] batman-adv: drop batman-adv specific version for in-tree module
Date: Fri, 15 May 2026 10:35:06 +0200	[thread overview]
Message-ID: <6294938.lOV4Wx5bFT@sven-desktop> (raw)
In-Reply-To: <20260515-no-upstream-version-bumps-v1-1-6aa349f8e949@narfation.org>

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

On Friday, 15 May 2026 10:00:00 CEST Sven Eckelmann wrote:
> diff --git a/net/batman-adv/main.c b/net/batman-adv/main.c
> index 2baf8e2c..5d27175a 100644
> --- a/net/batman-adv/main.c
> +++ b/net/batman-adv/main.c
> @@ -696,6 +696,5 @@ MODULE_LICENSE("GPL");
>  
>  MODULE_AUTHOR(BATADV_DRIVER_AUTHOR);
>  MODULE_DESCRIPTION(BATADV_DRIVER_DESC);
> -MODULE_VERSION(BATADV_SOURCE_VERSION);
>  MODULE_ALIAS_RTNL_LINK("batadv");
>  MODULE_ALIAS_GENL_FAMILY(BATADV_NL_NAME);

I was under the impression that I've removed the check for this version file 
in batctl a while ago - apparently, I haven't. We must therefore keep this 
"MODULE_VERSION" for a while in the in-tree batman-adv. I will do this now...

I will therefore drop this specific part of the patch. It just simplifies the 
patch and will focus only on the version bump.

Regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-05-15  8:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  8:00 [PATCH RFC batadv] batman-adv: drop batman-adv specific version for in-tree module Sven Eckelmann
2026-05-15  8:35 ` Sven Eckelmann [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=6294938.lOV4Wx5bFT@sven-desktop \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.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