From: Markus Elfring <Markus.Elfring@web.de>
To: Grygorii Tertychnyi <grygorii.tertychnyi@leica-geosystems.com>,
bsp-development.geo@leica-geosystems.com,
linux-i2c@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Peter Korsgaard <peter@korsgaard.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Grygorii Tertychnyi <grembeter@gmail.com>
Subject: Re: [PATCH v2] i2c: ocores: set IACK bit after core is enabled
Date: Mon, 20 May 2024 19:00:08 +0200 [thread overview]
Message-ID: <e98f8e4c-bd1f-43d8-aea9-52ea45c0d5c2@web.de> (raw)
In-Reply-To: <20240520153932.116731-1-grygorii.tertychnyi@leica-geosystems.com>
…
> Sometimes it causes failure for the very first message transfer, …
Would it be helpful to mention the term “data corruption” here?
https://lore.kernel.org/lkml/CAGFuAuwot_7+R=J4NC=0Z_48YZ-RTJjRUoQnSjZUvpt=AWF39Q@mail.gmail.com/
https://lkml.org/lkml/2024/5/20/549
> Fixes: 18f98b1e3147 ("[PATCH] i2c: New bus driver for the OpenCores I2C controller")
Will the text “[PATCH] ” be omitted from this tag for the final commit?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9#n145
Regards,
Markus
next prev parent reply other threads:[~2024-05-20 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 15:39 [PATCH v2] i2c: ocores: set IACK bit after core is enabled Grygorii Tertychnyi
2024-05-20 17:00 ` Markus Elfring [this message]
2024-05-20 18:20 ` Greg KH
2024-06-02 13:07 ` grygorii tertychnyi
2024-06-17 17:22 ` grygorii tertychnyi
2024-06-20 23:19 ` Andi Shyti
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=e98f8e4c-bd1f-43d8-aea9-52ea45c0d5c2@web.de \
--to=markus.elfring@web.de \
--cc=andrew@lunn.ch \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=grembeter@gmail.com \
--cc=grygorii.tertychnyi@leica-geosystems.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@korsgaard.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).