* [PATCH BlueZ] Fix URL for submitting patches
@ 2025-03-10 10:41 Andrew Sayers
2025-03-10 12:04 ` [BlueZ] " bluez.test.bot
2025-03-12 16:50 ` [PATCH BlueZ] " patchwork-bot+bluetooth
0 siblings, 2 replies; 3+ messages in thread
From: Andrew Sayers @ 2025-03-10 10:41 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Andrew Sayers
The previous URL is out of date, and now just says
"This file has moved to process/submitting-patches.rst"
---
HACKING | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/HACKING b/HACKING
index 29b136b34..5e07d91ea 100644
--- a/HACKING
+++ b/HACKING
@@ -116,7 +116,8 @@ The preferred way to send patches is by email, using git send-email:
# git config sendemail.to linux-bluetooth@vger.kernel.org
BlueZ rules for submitting patches follow most of the rules used by Linux kernel
-(https://www.kernel.org/doc/Documentation/SubmittingPatches) with some remarks:
+(https://www.kernel.org/doc/html/latest/process/submitting-patches.html)
+with some remarks:
1) Do *not* add "Signed-off-by" lines in your commit messages. BlueZ does not
use them, so including them is actually an error.
--
2.47.2
^ permalink raw reply related [flat|nested] 3+ messages in thread
* RE: [BlueZ] Fix URL for submitting patches
2025-03-10 10:41 [PATCH BlueZ] Fix URL for submitting patches Andrew Sayers
@ 2025-03-10 12:04 ` bluez.test.bot
2025-03-12 16:50 ` [PATCH BlueZ] " patchwork-bot+bluetooth
1 sibling, 0 replies; 3+ messages in thread
From: bluez.test.bot @ 2025-03-10 12:04 UTC (permalink / raw)
To: linux-bluetooth, kernel.org
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=942185
---Test result---
Test Summary:
CheckPatch PENDING 0.25 seconds
GitLint PENDING 0.25 seconds
BuildEll PASS 20.81 seconds
BluezMake PASS 1425.74 seconds
MakeCheck PASS 12.72 seconds
MakeDistcheck PASS 157.46 seconds
CheckValgrind PASS 214.46 seconds
CheckSmatch PASS 283.93 seconds
bluezmakeextell PASS 97.99 seconds
IncrementalBuild PENDING 0.34 seconds
ScanBuild PASS 859.08 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH BlueZ] Fix URL for submitting patches
2025-03-10 10:41 [PATCH BlueZ] Fix URL for submitting patches Andrew Sayers
2025-03-10 12:04 ` [BlueZ] " bluez.test.bot
@ 2025-03-12 16:50 ` patchwork-bot+bluetooth
1 sibling, 0 replies; 3+ messages in thread
From: patchwork-bot+bluetooth @ 2025-03-12 16:50 UTC (permalink / raw)
To: Andrew Sayers; +Cc: linux-bluetooth
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 10 Mar 2025 10:41:34 +0000 you wrote:
> The previous URL is out of date, and now just says
> "This file has moved to process/submitting-patches.rst"
> ---
> HACKING | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Here is the summary with links:
- [BlueZ] Fix URL for submitting patches
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d4749cfd7fba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-03-12 16:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-10 10:41 [PATCH BlueZ] Fix URL for submitting patches Andrew Sayers
2025-03-10 12:04 ` [BlueZ] " bluez.test.bot
2025-03-12 16:50 ` [PATCH BlueZ] " patchwork-bot+bluetooth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox