From: Phillip Potter <phil@philpotter.co.uk>
To: Jay Vadayath <jay@artiphishell.com>
Cc: phil@philpotter.co.uk, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH] cdrom: bound the device-supplied offset in cdrom_mrw_set_lba_space
Date: Wed, 11 Nov 2026 21:36:22 +0000 [thread overview]
Message-ID: <avTf1rFy2Ks8Gm3Z@equinox> (raw)
In-Reply-To: <CACd3oYMZ+umLbeK3q8oaJUwZHC4zbbFOe1YVEAq3s2v4B+d5Dw@mail.gmail.com>
On Tue, Nov 10, 2026 at 03:08:05PM -0700, Jay Vadayath wrote:
> Hi Phillip,
>
> Thank you for your response and for taking a look at this.
> I am happy to make the changes you requested.
> However, I wanted to clarify if you would like me to start a new email
> thread with the updated format ?
>
> Or was the idea to just follow up on this thread and repost the same
> email with the updated format ?
>
> Please let me know how you would like to proceed.
>
> Thank you.
>
>
Hi Jay,
So generally, I would submit a new patch, with the subject of:
[PATCH v2] cdrom: bound the device-supplied offset in cdrom_mrw_set_lba_space
And in that patch, mention the changes after the ---, i.e.
Signed-off-by: ...
---
Changes since v1: Updated commit message
Then include the rest of the patch as-is. Please run the completed patch
through scripts/checkpatch.pl as well, and make sure there are no
warnings.
Few more things:
- I seem to be getting duplicate e-mails from you, one in plain text and
one not. Please send only plain text to the mailing lists.
- Please put your reply underneath the original e-mail/portion of the
e-mail to which you're responding. Makes it easier to follow then and
is standard for kernel patch threads/commentaries etc.
I hope that helps.
Regards,
Phil Potter
prev parent reply other threads:[~2026-11-11 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 18:19 Jay Vadayath
2026-10-23 21:19 ` Phillip Potter
2026-10-24 16:51 ` Jay Vadayath
2026-11-10 21:47 ` Phillip Potter
2026-11-10 22:08 ` Jay Vadayath
2026-11-11 21:36 ` Phillip Potter [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=avTf1rFy2Ks8Gm3Z@equinox \
--to=phil@philpotter.co.uk \
--cc=jay@artiphishell.com \
--cc=linux-block@vger.kernel.org \
--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®