From: Sven Eckelmann <sven@narfation.org>
To: Simon Wunderlich <sw@simonwunderlich.de>,
davem@davemloft.net, Paolo Abeni <pabeni@redhat.com>
Cc: kuba@kernel.org, netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH 0/5] pull request for net: batman-adv 2025-03-13
Date: Tue, 18 Mar 2025 14:56:07 +0100 [thread overview]
Message-ID: <3809149.MHq7AAxBmi@ripper> (raw)
In-Reply-To: <a0f1deec-2770-4b51-ad2b-b3d0e846be25@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Simon Wunderlich <sw@simonwunderlich.de>,
davem@davemloft.net, Paolo Abeni <pabeni@redhat.com>
Cc: kuba@kernel.org, netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH 0/5] pull request for net: batman-adv 2025-03-13
Date: Tue, 18 Mar 2025 14:56:07 +0100 [thread overview]
Message-ID: <3809149.MHq7AAxBmi@ripper> (raw)
In-Reply-To: <a0f1deec-2770-4b51-ad2b-b3d0e846be25@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-18 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 16:17 [PATCH 0/5] pull request for net: batman-adv 2025-03-13 Simon Wunderlich
2025-03-13 16:17 ` [PATCH 1/5] batman-adv: fix panic during interface removal Simon Wunderlich
2025-03-13 16:17 ` [PATCH 2/5] batman-adv: Ignore neighbor throughput metrics in error case Simon Wunderlich
2025-03-13 16:17 ` [PATCH 3/5] batman-adv: Drop unmanaged ELP metric worker Simon Wunderlich
2025-03-13 16:17 ` [PATCH 4/5] batman-adv: Fix incorrect offset in batadv_tt_tvlv_ogm_handler_v1() Simon Wunderlich
2025-03-13 16:17 ` [PATCH 5/5] batman-adv: Ignore own maximum aggregation size during RX Simon Wunderlich
2025-03-18 11:05 ` [PATCH 0/5] pull request for net: batman-adv 2025-03-13 Paolo Abeni
2025-03-18 13:56 ` Sven Eckelmann [this message]
2025-03-18 13:56 ` Sven Eckelmann
2025-03-18 14:27 ` Paolo Abeni
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=3809149.MHq7AAxBmi@ripper \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sw@simonwunderlich.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.