From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Bjørn Mork" <bjorn@mork.no>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH v3] net: sfp: add SMBus I2C block support
Date: Mon, 5 Jan 2026 17:53:42 +0100 [thread overview]
Message-ID: <3c774e4d-b7a6-44e3-99f3-876f5ccb1ca3@gmail.com> (raw)
In-Reply-To: <aVvmu1YtiO9cXUw0@shell.armlinux.org.uk>
Hi Russell,
On 05.01.26 17:28, Russell King (Oracle) wrote:
> On Mon, Jan 05, 2026 at 04:12:42PM +0000, Jonas Jelonek wrote:
>> base-commit: c303e8b86d9dbd6868f5216272973292f7f3b7f1
>> prerequisite-patch-id: ae039dad1e17867fce9182b6b36ac3b1926b254a
> This seems to be almost useless information. While base-commit exists
> in the net-next tree, commit ae039dad1e17867fce9182b6b36ac3b1926b254a
> doesn't exist in either net-next nor net trees.
>
> My guess is you applied Maxime's patch locally, and that is the
> commit ID of that patch.
This was supposed to be the stable patch-id obtained with
'git patch-id --stable'.
> Given that Maxime's patch is targetting the net tree (because it's
> a fix), and your patch is new development, so is for net-next, you
> either need to:
> - wait until Maxime's patch has been merged, and then the net tree
> has been merged into net-next.
> or:
> - resend without Maxime's patch.
>
> In either case, please read https://docs.kernel.org/process/maintainer-netdev.html
> In particular, the salient points are:
> - no resends in under 24 hours (see point 1.6.7)
> - specify the tree that your patch is targetting in the subject line
> (see point 1.6.1) E.g. [PATCH net-next v...] net: blah blah
>
> Thanks.
>
Ack. I'll fix the points you mentioned.
Thanks for your patience.
Best,
Jonas
next prev parent reply other threads:[~2026-01-05 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:12 Jonas Jelonek
2026-01-05 16:28 ` Russell King (Oracle)
2026-01-05 16:53 ` Jonas Jelonek [this message]
2026-01-05 17:13 ` Russell King (Oracle)
2026-01-05 23:52 ` Jakub Kicinski
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=3c774e4d-b7a6-44e3-99f3-876f5ccb1ca3@gmail.com \
--to=jelonek.jonas@gmail.com \
--cc=andrew@lunn.ch \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--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®