[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3809149.MHq7AAxBmi@ripper>
Date: Tue, 18 Mar 2025 14:56:07 +0100
From: Sven Eckelmann <sven@...fation.org>
To: Simon Wunderlich <sw@...onwunderlich.de>, davem@...emloft.net,
Paolo Abeni <pabeni@...hat.com>
Cc: kuba@...nel.org, netdev@...r.kernel.org, b.a.t.m.a.n@...ts.open-mesh.org
Subject: Re: [PATCH 0/5] pull request for net: batman-adv 2025-03-13
On Tuesday, 18 March 2025 12:05:52 CET Paolo Abeni wrote:
> The series does not apply cleanly to the net tree, could you please
> rebase it?
$ git log -1 --oneline
9a81fc3480bf (HEAD, net/main) ipv6: Set errno after ip_fib_metrics_init() in ip6_route_info_create().
$ git pull --no-ff git://git.open-mesh.org/linux-merge.git tags/batadv-net-pullrequest-20250313
>From git://git.open-mesh.org/linux-merge
* tag batadv-net-pullrequest-20250313 -> FETCH_HEAD
Merge made by the 'ort' strategy.
net/batman-adv/bat_iv_ogm.c | 3 +--
net/batman-adv/bat_v_ogm.c | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
So, it works perfectly fine for me .
I understand that it is confusing that that Simon send a PR with 5 patches
mentioned. It is actually only 1 patch - 4 were already submitted in the last
PR. But still, the PR seems to apply cleanly for me.
Any hints how to reproduce your problem?
> While at it, could you please include the target tree in the subj prefix?
It currently mentions net in the subject. But I think you mean to change it
from "[PATCH 0/5] pull request for net: batman-adv 2025-03-13" to
"[PATCH net 0/5] pull request: batman-adv 2025-03-13". Or which exact format
do you prefer?
Kind regards,
Sven
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists