From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Markus Elfring <Markus.Elfring@web.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
linux-sound@vger.kernel.org
Cc: Bard Liao <yung-chuan.liao@linux.intel.com>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Vinod Koul <vkoul@kernel.org>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: soundwire: bus: fix off-by-one when allocating slave IDs
Date: Mon, 12 Jan 2026 11:13:47 +0000 [thread overview]
Message-ID: <62e256c4-a616-4c80-ba29-43f767f4d342@opensource.cirrus.com> (raw)
In-Reply-To: <35084885-09dc-4255-8ec9-ba23c3a2a925@web.de>
On 12/01/2026 10:55 am, Markus Elfring wrote:
>> Sorry, if that was unclear. The link is a real link to the documentation
>> which says:
>>
>> - The body of the explanation, line wrapped at 75 columns, which will
>> be copied to the permanent changelog to describe this patch.
>>
>> The rules that we write down are simplified guidelines which are designed
>> to be easy explain. 75 is the upper bound where checkpatch will complain.
> …
>
> Can we benefit a bit more from this system configuration setting
Why is this wrapped at column 64?
> instead of performing word wrapping at around the column 67 here?
>
> Regards,
> Markus
>
next prev parent reply other threads:[~2026-01-12 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 20:19 [PATCH] " Harshit Mogalapalli
2026-01-11 9:27 ` Markus Elfring
2026-01-12 8:26 ` Dan Carpenter
2026-01-12 8:49 ` Dan Carpenter
2026-01-12 10:55 ` Markus Elfring
2026-01-12 11:13 ` Richard Fitzgerald [this message]
2026-01-13 11:24 ` Vinod Koul
2026-01-12 9:56 ` [PATCH] " Charles Keepax
2026-01-13 11:29 ` Vinod Koul
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=62e256c4-a616-4c80-ba29-43f767f4d342@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=Markus.Elfring@web.de \
--cc=ckeepax@opensource.cirrus.com \
--cc=dan.carpenter@linaro.org \
--cc=error27@gmail.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.com \
/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®