From: Phillip Potter <phil@philpotter.co.uk>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: hch@infradead.org, axboe@kernel.dk, linux-kernel@vger.kernel.org,
lumip@lumip.de, linux-block@vger.kernel.org
Subject: Re: [PATCH v2] drivers/cdrom: improved ioctl for media change detection
Date: Fri, 10 Sep 2021 00:00:28 +0100 [thread overview]
Message-ID: <YTqSDICXcjdrC+vt@equinox> (raw)
In-Reply-To: <409876e1-1293-932d-8d37-0211bef07749@infradead.org>
On Wed, Sep 08, 2021 at 05:42:30PM -0700, Randy Dunlap wrote:
> Documentation/process/coding-style.rst says:
>
> The preferred limit on the length of a single line is 80 columns.
>
> checkpatch only checks lines > 100 columns since that is OK in a few
> cases, like a long quoted string.
>
> So try to limit line lengths to 80 columns unless there is some
> other reason not to do that.
>
Dear Randy,
Thank you for clarifying this, appreciate it. Will try and bear it in
mind in future :-)
Regards,
Phil
next parent reply other threads:[~2021-09-09 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YTcILRYw/AKen0X4@infradead.org>
[not found] ` <20210909001721.2030-1-phil@philpotter.co.uk>
[not found] ` <409876e1-1293-932d-8d37-0211bef07749@infradead.org>
2021-09-09 23:00 ` Phillip Potter [this message]
[not found] ` <20210909180553.8299-1-lumip@lumip.de>
2021-09-09 23:20 ` [PATCH v2] drivers/cdrom: improved ioctl for media change detection Phillip Potter
[not found] ` <10f60086-2be0-d26d-dfa6-fe128772a409@infradead.org>
2021-09-10 7:59 ` Phillip Potter
[not found] <20210829143735.512146-1-lumip@lumip.de>
[not found] ` <65bf6d1a-f65d-910c-60c7-0a4911a52e9a@kernel.dk>
2021-09-06 22:57 ` Phillip Potter
2021-09-08 23:51 ` Phillip Potter
2021-09-09 18:04 ` Lukas Prediger
2021-09-09 23:07 ` Phillip Potter
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=YTqSDICXcjdrC+vt@equinox \
--to=phil@philpotter.co.uk \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumip@lumip.de \
--cc=rdunlap@infradead.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