linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
	Avi Fishman <avifishman70@gmail.com>,
	Tomer Maimon <tmaimon77@gmail.com>,
	Tali Perry <tali.perry1@gmail.com>,
	Patrick Venture <venture@google.com>,
	Nancy Yuen <yuenn@google.com>,
	Benjamin Fair <benjaminfair@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] i2c: npcm7xx: Annotate register field definitions with longer names
Date: Tue, 1 Nov 2022 13:45:17 +0100	[thread overview]
Message-ID: <Y2EU3aLbwfq8wXUv@shikoro> (raw)
In-Reply-To: <20221008125924.1220203-2-j.neuschaefer@gmx.net>

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

On Sat, Oct 08, 2022 at 02:59:24PM +0200, Jonathan Neuschäfer wrote:
> To make the code easier to understand, add longer names to the
> definitions of register fields. These longer names are based on source
> code published by DELL/AESS for WPCM450, but should apply just as well
> to NPCM7xx and NPCM8xx.
> 
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>

Applied to for-next, thanks!


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

  parent reply	other threads:[~2022-11-01 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 12:59 [PATCH 1/2] i2c: npcm7xx: Group bank 0/1 registers together for readability Jonathan Neuschäfer
2022-10-08 12:59 ` [PATCH 2/2] i2c: npcm7xx: Annotate register field definitions with longer names Jonathan Neuschäfer
2022-10-11  6:08   ` Tali Perry
2022-11-01 12:45   ` Wolfram Sang [this message]
2022-10-11  6:08 ` [PATCH 1/2] i2c: npcm7xx: Group bank 0/1 registers together for readability Tali Perry
2022-11-01 12:45 ` Wolfram Sang

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=Y2EU3aLbwfq8wXUv@shikoro \
    --to=wsa@kernel.org \
    --cc=avifishman70@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=j.neuschaefer@gmx.net \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tali.perry1@gmail.com \
    --cc=tmaimon77@gmail.com \
    --cc=venture@google.com \
    --cc=yuenn@google.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;
as well as URLs for NNTP newsgroup(s).