mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Potter <phil@philpotter.co.uk>
To: Steven Davis <goldside000@outlook.com>
Cc: linux-kernel@vger.kernel.org, phil@philpotter.co.uk
Subject: Re: [PATCH v2] cdrom: Fix typo, 'devicen' to 'device'
Date: Sun, 29 Dec 2024 18:32:57 +0000	[thread overview]
Message-ID: <Z3GV2W_MUOw5BrtR@equinox> (raw)
In-Reply-To: <20241229165744.21725-1-goldside000@outlook.com>

On Sun, Dec 29, 2024 at 04:57:54PM +0000, Steven Davis wrote:
> Nothing big here, just a typo that really bugged me. :)
> 
> I assume whoever wrote this was trying to make a new
> line, so I went ahead and put a back slash in it.
> 
> Signed-off-by: Steven Davis <goldside000@outlook.com>
> ---
> V1 -> V2: Add directory I changed to subject
> 
>  drivers/cdrom/cdrom.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
> index 6a99a459b..2863e5db2 100644
> --- a/drivers/cdrom/cdrom.c
> +++ b/drivers/cdrom/cdrom.c
> @@ -1106,7 +1106,7 @@ int open_for_data(struct cdrom_device_info *cdi)
>  		}
>  	}
>  
> -	cd_dbg(CD_OPEN, "all seems well, opening the devicen");
> +	cd_dbg(CD_OPEN, "all seems well, opening the device\n");
>  
>  	/* all seems well, we can open the device */
>  	ret = cdo->open(cdi, 0); /* open for data */
> -- 
> 2.39.5
> 

Hi Steven,

Thank you for the patch, looks good to me. I will forward onto Jens for
inclusion upstream.

Reviewed-by: Phillip Potter <phil@philpotter.co.uk>

On another note though: The raw patch submission e-mail body seems to have
some encoding issues, evidenced by the presence of extra content on empty
lines:
=20
-	cd_dbg(CD_OPEN, "all seems well, opening the devicen");
+	cd_dbg(CD_OPEN, "all seems well, opening the device\n");
=20

Also, it triggers checkpatch for the same reason:
ERROR: patch seems to be corrupt (line wrapped?)
#165: FILE: drivers/cdrom/cdrom.c:1107:
=20

total: 1 errors, 0 warnings, 11 lines checked

In this instance, happy to send on from yourself with this corrected,
but please do look into why this is happening - it is possibly related
to your e-mail client.

Many thanks.

Regards,
Phil

  reply	other threads:[~2024-12-29 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29 16:57 Steven Davis
2024-12-29 18:32 ` Phillip Potter [this message]
2024-12-29 18:43 ` Steven Davis
2024-12-29 19:01   ` Phillip Potter
2024-12-29 19:11     ` Steven Davis

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=Z3GV2W_MUOw5BrtR@equinox \
    --to=phil@philpotter.co.uk \
    --cc=goldside000@outlook.com \
    --cc=linux-kernel@vger.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®