From: Wolfram Sang <wsa@kernel.org>
To: Tyrone Ting <warp5tw@gmail.com>
Cc: avifishman70@gmail.com, tmaimon77@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
andriy.shevchenko@linux.intel.com, jarkko.nikula@linux.intel.com,
semen.protsenko@linaro.org, sven@svenpeter.dev, jsd@semihalf.com,
lukas.bulwahn@gmail.com, olof@lixom.net, arnd@arndb.de,
tali.perry@nuvoton.com, Avi.Fishman@nuvoton.com,
tomer.maimon@nuvoton.com, KWLIU@nuvoton.com, JJLIU0@nuvoton.com,
kfting@nuvoton.com, openbmc@lists.ozlabs.org,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, krzysztof.kozlowski@canonical.com,
jie.deng@intel.com
Subject: Re: [PATCH v4 2/9] i2c: npcm: Change the way of getting GCR regmap
Date: Tue, 17 May 2022 08:04:13 +0200 [thread overview]
Message-ID: <YoM63XoYZbFGJ8s7@kunai> (raw)
In-Reply-To: <CACD3sJa3koHGsC3PBbfZuBhTfVHhjF=3g3YysxZ0+TvQ1qwfyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
> After reviewing these two links, we decided to keep only the author's
> SoB for each commit.
>
> https://lore.kernel.org/lkml/YiCZlhJoXPLpQ6%2FD@smile.fi.intel.com/
> https://lore.kernel.org/lkml/YiCb7LNY9tmMCZx7@smile.fi.intel.com/
When Andy said "chain is wrong", he meant the order. You must add your
SoB, otherwise I can't take the patches. But yours should be last. The
SoBs need to be in the order people worked on it.
Does that make sense to you?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Tyrone Ting <warp5tw@gmail.com>
Cc: tmaimon77@gmail.com, devicetree@vger.kernel.org,
tali.perry1@gmail.com, jsd@semihalf.com,
krzysztof.kozlowski+dt@linaro.org, benjaminfair@google.com,
krzysztof.kozlowski@canonical.com, openbmc@lists.ozlabs.org,
JJLIU0@nuvoton.com, lukas.bulwahn@gmail.com,
tomer.maimon@nuvoton.com, KWLIU@nuvoton.com, arnd@arndb.de,
sven@svenpeter.dev, robh+dt@kernel.org, Avi.Fishman@nuvoton.com,
andriy.shevchenko@linux.intel.com, semen.protsenko@linaro.org,
jie.deng@intel.com, avifishman70@gmail.com, venture@google.com,
linux-kernel@vger.kernel.org, kfting@nuvoton.com,
tali.perry@nuvoton.com, jarkko.nikula@linux.intel.com,
olof@lixom.net, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v4 2/9] i2c: npcm: Change the way of getting GCR regmap
Date: Tue, 17 May 2022 08:04:13 +0200 [thread overview]
Message-ID: <YoM63XoYZbFGJ8s7@kunai> (raw)
In-Reply-To: <CACD3sJa3koHGsC3PBbfZuBhTfVHhjF=3g3YysxZ0+TvQ1qwfyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
> After reviewing these two links, we decided to keep only the author's
> SoB for each commit.
>
> https://lore.kernel.org/lkml/YiCZlhJoXPLpQ6%2FD@smile.fi.intel.com/
> https://lore.kernel.org/lkml/YiCb7LNY9tmMCZx7@smile.fi.intel.com/
When Andy said "chain is wrong", he meant the order. You must add your
SoB, otherwise I can't take the patches. But yours should be last. The
SoBs need to be in the order people worked on it.
Does that make sense to you?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-17 6:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:16 [PATCH v4 0/9] i2c: npcm: Bug fixes timeout, spurious interrupts Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 1/9] dt-bindings: i2c: npcm: support NPCM845 Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-11 15:24 ` Rob Herring
2022-05-11 15:24 ` Rob Herring
2022-05-12 1:31 ` Tyrone Ting
2022-05-12 1:31 ` Tyrone Ting
2022-05-13 8:26 ` Krzysztof Kozlowski
2022-05-10 9:16 ` [PATCH v4 2/9] i2c: npcm: Change the way of getting GCR regmap Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 10:08 ` Andy Shevchenko
2022-05-10 10:08 ` Andy Shevchenko
2022-05-11 1:34 ` Tyrone Ting
2022-05-11 1:34 ` Tyrone Ting
2022-05-16 19:48 ` Wolfram Sang
2022-05-16 19:48 ` Wolfram Sang
2022-05-17 1:05 ` Tyrone Ting
2022-05-17 1:05 ` Tyrone Ting
2022-05-17 6:04 ` Wolfram Sang [this message]
2022-05-17 6:04 ` Wolfram Sang
2022-05-17 6:09 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 3/9] i2c: npcm: Remove unused variable clk_regmap Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 4/9] i2c: npcm: Fix timeout calculation Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 5/9] i2c: npcm: Add tx complete counter Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 6/9] i2c: npcm: Correct register access width Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 7/9] i2c: npcm: Handle spurious interrupts Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 10:14 ` Andy Shevchenko
2022-05-10 10:14 ` Andy Shevchenko
2022-05-11 5:37 ` Tyrone Ting
2022-05-11 5:37 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 8/9] i2c: npcm: Remove own slave addresses 2:10 Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
2022-05-10 10:19 ` Andy Shevchenko
2022-05-10 10:19 ` Andy Shevchenko
2022-05-11 1:39 ` Tyrone Ting
2022-05-11 1:39 ` Tyrone Ting
2022-05-16 1:23 ` Tyrone Ting
2022-05-16 1:23 ` Tyrone Ting
2022-05-10 9:16 ` [PATCH v4 9/9] i2c: npcm: Support NPCM845 Tyrone Ting
2022-05-10 9:16 ` Tyrone Ting
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=YoM63XoYZbFGJ8s7@kunai \
--to=wsa@kernel.org \
--cc=Avi.Fishman@nuvoton.com \
--cc=JJLIU0@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jie.deng@intel.com \
--cc=jsd@semihalf.com \
--cc=kfting@nuvoton.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=olof@lixom.net \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=sven@svenpeter.dev \
--cc=tali.perry1@gmail.com \
--cc=tali.perry@nuvoton.com \
--cc=tmaimon77@gmail.com \
--cc=tomer.maimon@nuvoton.com \
--cc=venture@google.com \
--cc=warp5tw@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.