From: patchwork-bot+netdevbpf@kernel.org
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
andrew@lunn.ch, tmgross@umich.edu
Subject: Re: [PATCH net-next] rust: phy: use `srctree`-relative links
Date: Sat, 27 Jan 2024 14:30:29 +0000 [thread overview]
Message-ID: <170636582908.20177.384966136875153449.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240125014502.3527275-1-fujita.tomonori@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 25 Jan 2024 10:45:01 +0900 you wrote:
> The relative paths like the following are bothersome and don't work
> with `O=` builds:
>
> //! C headers: [`include/linux/phy.h`](../../../../../../../include/linux/phy.h).
>
> This updates such links by using the `srctree`-relative link feature
> introduced in 6.8-rc1 like:
>
> [...]
Here is the summary with links:
- [net-next] rust: phy: use `srctree`-relative links
https://git.kernel.org/netdev/net-next/c/1d4046b57142
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-01-27 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 1:45 [PATCH net-next] rust: phy: use `srctree`-relative links FUJITA Tomonori
2024-01-25 1:45 ` [PATCH net-next] rust: phy: use VTABLE_DEFAULT_ERROR FUJITA Tomonori
2024-01-25 2:27 ` Trevor Gross
2024-01-25 17:42 ` Andrew Lunn
2024-01-26 1:03 ` Trevor Gross
2024-01-27 14:30 ` patchwork-bot+netdevbpf
2024-01-25 2:24 ` [PATCH net-next] rust: phy: use `srctree`-relative links Trevor Gross
2024-01-27 14:30 ` patchwork-bot+netdevbpf [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=170636582908.20177.384966136875153449.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=fujita.tomonori@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).