linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linuxkernel@fbautosys.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/5] Add Parity bit Calculation to regmaps
Date: Wed, 5 Jan 2022 16:51:09 +0000	[thread overview]
Message-ID: <YdXMfX5xayAfRWXe@sirena.org.uk> (raw)
In-Reply-To: <20211222184340.1907240-2-linuxkernel@fbautosys.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

On Wed, Dec 22, 2021 at 06:43:36PM +0000, linuxkernel@fbautosys.co.uk wrote:
> From: Christopher Tyerman <c.tyerman@firebladeautomationsystems.co.uk>
> 
> regmap.h
> 
> Added bitmasks "parity_read_mask" and "parity_write_mask" for read
> and write operations to regmap_config bit mask defines location of
> the parity bit.
> 
> Added optional callback "parity_calc" to regmap_config to
> calculate parity bit value

This is still more a list of changes in the code rather than a normal
changelog which is making it really hard to review - I'm getting lost
with the patch description trying to figure out what the idea here is or
how this is all supposed to fit together.  Like I said last time please
look at submitting-patches.rst.  It's probably also useful to look at
how other kernel changelogs are written and follow a similar style.

Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-01-05 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 18:43 [RFC PATCH v2 0/5] regmap: Add Parity bit Calculation to regmaps linuxkernel
2021-12-22 18:43 ` [RFC PATCH v2 1/5] " linuxkernel
2022-01-05 16:51   ` Mark Brown [this message]
2021-12-22 18:43 ` [RFC PATCH v2 2/5] Altered regmap_format_X_X_write functions to account for padding bits linuxkernel
2021-12-22 18:43 ` [RFC PATCH v2 3/5] Added setting of writemap to formatted write linuxkernel
2021-12-22 18:43 ` [RFC PATCH v2 4/5] Add Parity Calculation " linuxkernel
2021-12-22 18:43 ` [RFC PATCH v2 5/5] Add parser for X_9 formats linuxkernel

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=YdXMfX5xayAfRWXe@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxkernel@fbautosys.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;
as well as URLs for NNTP newsgroup(s).