From: Salah Triki <salah.triki@gmail.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] bcma: Use managed APIs
Date: Sat, 19 Jul 2025 19:38:05 +0100 [thread overview]
Message-ID: <aHvmDZjmhxG3EJg9@pc> (raw)
In-Reply-To: <1cb5c9e8-9894-43e6-ba3b-755a7d1dd56b@oss.qualcomm.com>
On Sat, Jul 19, 2025 at 10:21:59AM -0700, Jeff Johnson wrote:
>
> 1) When you post a new version of a patch, please do NOT have it be
> In-Reply-To any previous messages. Each version of a patch should start a
> separate e-mail thread. The guidance at
> <https://www.kernel.org/doc/html/latest/process/submitting-patches.html#explicit-in-reply-to-headers>
> seems outdated.
>
> 2) Most maintainers will not accept patches which make such a big semantic
> change without actually testing the change on hardware.
Thanx for information
Best regards,
Salah Triki
prev parent reply other threads:[~2025-07-19 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 14:43 [PATCH] bcma: Use managed APIs Salah Triki
2025-07-19 15:52 ` [PATCH v2] " Salah Triki
2025-07-19 15:54 ` Johannes Berg
2025-07-19 16:19 ` [PATCH v3] " Salah Triki
2025-07-19 17:21 ` Jeff Johnson
2025-07-19 18:38 ` Salah Triki [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=aHvmDZjmhxG3EJg9@pc \
--to=salah.triki@gmail.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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