From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Saravana Kannan <saravanak@google.com>,
kernel@collabora.com, linux-kernel@vger.kernel.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH v2 2/2] driver core: Don't log intentional skip of device link creation as error
Date: Wed, 16 Oct 2024 07:37:55 +0200 [thread overview]
Message-ID: <2024101645-crushed-defection-0782@gregkh> (raw)
In-Reply-To: <20241015-fwdevlink-probed-no-err-v2-2-756c5e9cf55c@collabora.com>
On Tue, Oct 15, 2024 at 05:27:18PM -0400, Nícolas F. R. A. Prado wrote:
> Commit ac66c5bbb437 ("driver core: Allow only unprobed consumers for
> SYNC_STATE_ONLY device links") introduced an early return in
> device_link_add() to prevent useless links from being created. However
> the calling function fw_devlink_create_devlink() unconditionally prints
> an error if device_link_add() didn't create a link, even in this case
> where it is intentionally skipping the link creation.
>
> Add a check to detect if the link wasn't created intentionally and in
> that case don't log an error.
>
> Fixes: ac66c5bbb437 ("driver core: Allow only unprobed consumers for SYNC_STATE_ONLY device links")
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> ---
> drivers/base/core.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You have marked a patch with a "Fixes:" tag for a commit that is in an
older released kernel, yet you do not have a cc: stable line in the
signed-off-by area at all, which means that the patch will not be
applied to any older kernel releases. To properly fix this, please
follow the documented rules in the
Documentation/process/stable-kernel-rules.rst file for how to resolve
this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2024-10-16 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 21:27 [PATCH v2 0/2] driver core: Avoid false-positive errors for intentionally skipped links Nícolas F. R. A. Prado
2024-10-15 21:27 ` [PATCH v2 1/2] driver core: Create device_link_is_useless() helper Nícolas F. R. A. Prado
2024-10-15 21:27 ` [PATCH v2 2/2] driver core: Don't log intentional skip of device link creation as error Nícolas F. R. A. Prado
2024-10-16 5:37 ` Greg Kroah-Hartman [this message]
2024-10-16 11:19 ` [PATCH v2 0/2] driver core: Avoid false-positive errors for intentionally skipped links Jon Hunter
2024-10-23 20:03 ` Nícolas F. R. A. Prado
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=2024101645-crushed-defection-0782@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=rafael@kernel.org \
--cc=saravanak@google.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