From: Steven Davis <goldside000@outlook.com>
To: Steven Davis <goldside000@outlook.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"phil@philpotter.co.uk" <phil@philpotter.co.uk>
Subject: Re: [PATCH v2] cdrom: Fix typo, 'devicen' to 'device'
Date: Sun, 29 Dec 2024 18:43:20 +0000 [thread overview]
Message-ID: <20241229184232.22491-1-goldside000@outlook.com> (raw)
In-Reply-To: <20241229165744.21725-1-goldside000@outlook.com>
On Sun, Dec 29, 2024 at 18:32:57 +0000, Phillip Potter wrote:
> 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.
That's strange, I've been using git send-email, and that's the first time
that's ever happened. I ran checkpatch before I sent it, and it didn't say
anything.
I thank you for accepting my patch, nonetheless!
Steven
next prev parent reply other threads:[~2024-12-29 18:43 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
2024-12-29 18:43 ` Steven Davis [this message]
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=20241229184232.22491-1-goldside000@outlook.com \
--to=goldside000@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@philpotter.co.uk \
/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®