From: Dragan Simic <dsimic@manjaro.org>
To: linux-spi@vger.kernel.org, linux-rockchip@lists.infradead.org
Cc: broonie@kernel.org, heiko@sntech.de, gregkh@linuxfoundation.org,
rafael@kernel.org, oss@helene.moe,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: Fix a typo in __dev_probe_failed() comments
Date: Tue, 08 Oct 2024 21:02:38 +0200 [thread overview]
Message-ID: <76254295771cb4ea5644f2ce4a30f0d7@manjaro.org> (raw)
In-Reply-To: <cec37f5568afaef8fca2d35bb01c90556ccbb4f4.1728408464.git.dsimic@manjaro.org>
On 2024-10-08 19:29, Dragan Simic wrote:
> Fix a small typo in one of the variable names found in the comment
> block
> inside the __dev_probe_failed() function.
>
> Signed-off-by: Dragan Simic <dsimic@manjaro.org>
> ---
>
> Notes:
> This is an incremental patch for the patch series [1] that's been
> already
> merged, so it should be applied on top of the series.
>
> [1]
> https://lore.kernel.org/linux-rockchip/cover.1727601608.git.dsimic@manjaro.org/T/#u
Please disregard this patch, Mark will have both spotted typos [2]
fixed by hand. [3] Sorry for the noise.
[2]
https://lore.kernel.org/linux-spi/e8cbbf877cc0e6838afd2d6de3b7bfa1@manjaro.org/
[3]
https://lore.kernel.org/linux-spi/ZwVt9e44jc3CQaV1@finisterre.sirena.org.uk/
> drivers/base/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index 5f156a9a10a4..a84a7b952cfd 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -4989,7 +4989,7 @@ static void __dev_probe_failed(const struct
> device *dev, int err, bool fatal,
> /*
> * On x86_64 and possibly on other architectures, va_list is actually
> a
> * size-1 array containing a structure. As a result, function
> parameter
> - * vargps decays from T[1] to T*, and &vargsp has type T** rather
> than
> + * vargsp decays from T[1] to T*, and &vargsp has type T** rather
> than
> * T(*)[1], which is expected by its assignment to vaf.va below.
> *
> * One standard way to solve this mess is by creating a copy in a
> local
prev parent reply other threads:[~2024-10-08 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 17:29 Dragan Simic
2024-10-08 19:02 ` Dragan Simic [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=76254295771cb4ea5644f2ce4a30f0d7@manjaro.org \
--to=dsimic@manjaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=oss@helene.moe \
--cc=rafael@kernel.org \
/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
all inboxes | Powered by JetHome®