From: Jakub Kicinski <kuba@kernel.org>
To: Jonas Jelonek <jelonek.jonas@gmail.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
"Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"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 15:52:15 -0800 [thread overview]
Message-ID: <20260105155215.6e6e1456@kernel.org> (raw)
In-Reply-To: <aVvxSa2volDcLPZE@shell.armlinux.org.uk>
On Mon, 5 Jan 2026 17:13:45 +0000 Russell King (Oracle) wrote:
> > > 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'.
>
> Hmm, didn't know about that... but in this context, I wonder how
> useful it is. As a maintainer, given that patches submitted don't
> specify their patch-id, tracking down which patch is the
> pre-requisit would be a mammoth task [...]
+1, please wait for any pre-requisites to be in the tree before posting.
If you'd like to get early reviews send as RFC. Note that net gets
merged into net-next every Thu (in case the dependency is cross-tree
this is an extra wait).
prev parent reply other threads:[~2026-01-05 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:12 [PATCH v3] net: sfp: add SMBus I2C block support Jonas Jelonek
2026-01-05 16:28 ` Russell King (Oracle)
2026-01-05 16:53 ` Jonas Jelonek
2026-01-05 17:13 ` Russell King (Oracle)
2026-01-05 23:52 ` Jakub Kicinski [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=20260105155215.6e6e1456@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jelonek.jonas@gmail.com \
--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