From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: warp5tw@gmail.com
Cc: avifishman70@gmail.com, tmaimon77@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, andi.shyti@kernel.org, wsa@kernel.org,
rand.sec96@gmail.com, wsa+renesas@sang-engineering.com,
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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/6] i2c: npcm: correct the read/write operation procedure
Date: Fri, 20 Sep 2024 17:30:50 +0300 [thread overview]
Message-ID: <Zu2HGte_05AA6yky@smile.fi.intel.com> (raw)
In-Reply-To: <20240920101820.44850-2-kfting@nuvoton.com>
On Fri, Sep 20, 2024 at 06:18:15PM +0800, warp5tw@gmail.com wrote:
> From: Tyrone Ting <kfting@nuvoton.com>
>
> From: Tyrone Ting <kfting@nuvoton.com>
Something wrong with your email setup. This patch may not be applied in this form.
But before (re-)sending, wait for others to comment (up to 1 week).
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: warp5tw@gmail.com
Cc: KWLIU@nuvoton.com, tomer.maimon@nuvoton.com,
linux-kernel@vger.kernel.org, benjaminfair@google.com,
wsa+renesas@sang-engineering.com, avifishman70@gmail.com,
venture@google.com, openbmc@lists.ozlabs.org, kfting@nuvoton.com,
JJLIU0@nuvoton.com, tali.perry@nuvoton.com,
tali.perry1@gmail.com, wsa@kernel.org, andi.shyti@kernel.org,
linux-i2c@vger.kernel.org, Avi.Fishman@nuvoton.com,
rand.sec96@gmail.com, tmaimon77@gmail.com
Subject: Re: [PATCH v4 1/6] i2c: npcm: correct the read/write operation procedure
Date: Fri, 20 Sep 2024 17:30:50 +0300 [thread overview]
Message-ID: <Zu2HGte_05AA6yky@smile.fi.intel.com> (raw)
In-Reply-To: <20240920101820.44850-2-kfting@nuvoton.com>
On Fri, Sep 20, 2024 at 06:18:15PM +0800, warp5tw@gmail.com wrote:
> From: Tyrone Ting <kfting@nuvoton.com>
>
> From: Tyrone Ting <kfting@nuvoton.com>
Something wrong with your email setup. This patch may not be applied in this form.
But before (re-)sending, wait for others to comment (up to 1 week).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-20 14:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 10:18 [PATCH v4 0/6] i2c: npcm: read/write operation, checkpatch warp5tw
2024-09-20 10:18 ` [PATCH v4 1/6] i2c: npcm: correct the read/write operation procedure warp5tw
2024-09-20 14:30 ` Andy Shevchenko [this message]
2024-09-20 14:30 ` Andy Shevchenko
2024-09-23 1:51 ` Tyrone Ting
2024-09-23 1:51 ` Tyrone Ting
2024-09-25 20:19 ` Andi Shyti
2024-09-25 20:19 ` Andi Shyti
2024-09-27 1:59 ` Tyrone Ting
2024-09-27 1:59 ` Tyrone Ting
2024-09-20 10:18 ` [PATCH v4 2/6] i2c: npcm: use a software flag to indicate a BER condition warp5tw
2024-09-25 20:22 ` Andi Shyti
2024-09-25 20:22 ` Andi Shyti
2024-09-27 2:01 ` Tyrone Ting
2024-09-27 2:01 ` Tyrone Ting
2024-09-20 10:18 ` [PATCH v4 3/6] i2c: npcm: Modify timeout evaluation mechanism warp5tw
2024-09-25 20:24 ` Andi Shyti
2024-09-25 20:24 ` Andi Shyti
2024-09-27 2:03 ` Tyrone Ting
2024-09-27 2:03 ` Tyrone Ting
2024-09-20 10:18 ` [PATCH v4 4/6] i2c: npcm: Modify the client address assignment warp5tw
2024-09-20 14:32 ` Andy Shevchenko
2024-09-20 14:32 ` Andy Shevchenko
2024-09-23 1:59 ` Tyrone Ting
2024-09-23 1:59 ` Tyrone Ting
2024-09-23 8:25 ` Andy Shevchenko
2024-09-23 8:25 ` Andy Shevchenko
2024-09-20 10:18 ` [PATCH v4 5/6] i2c: npcm: use i2c frequency table warp5tw
2024-09-20 10:18 ` [PATCH v4 6/6] i2c: npcm: Enable slave in eob interrupt warp5tw
2024-09-20 10:18 ` warp5tw
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=Zu2HGte_05AA6yky@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Avi.Fishman@nuvoton.com \
--cc=JJLIU0@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=andi.shyti@kernel.org \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=kfting@nuvoton.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=rand.sec96@gmail.com \
--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=wsa+renesas@sang-engineering.com \
--cc=wsa@kernel.org \
--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.