From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: vigneshr@ti.com, aaro.koskinen@iki.fi, andreas@kemnade.info,
khilman@baylibre.com, rogerq@kernel.org, tony@atomide.com,
jmkrzyszt@gmail.com, andi.shyti@kernel.org,
miaoqinglang@huawei.com, grygorii.strashko@ti.com,
wsa@kernel.org
Cc: linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH 0/2] i2c: omap: 2 Fixes
Date: Sat, 5 Jul 2025 09:57:36 +0200 [thread overview]
Message-ID: <cover.1751701715.git.christophe.jaillet@wanadoo.fr> (raw)
This small serie is a follow-up of [1].
For an unkwown reason I don't feel really confident with these patches.
Maybe because one is really old and the other one is related to
pm, which ordering is sometimes tricky (from my PoV at least).
They are compile tested only.
So review with care ;-)
[1]: https://lore.kernel.org/all/vhhxtsspywvuzkfgbn52hysghd6tdxhk32wv3wcnlqwhskto3f@h2bbhek3s4s3/
Christophe JAILLET (2):
i2c: omap: Handle omap_i2c_init() errors in omap_i2c_probe()
i2c: omap: Fix an error handling path in omap_i2c_probe()
drivers/i2c/busses/i2c-omap.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--
2.50.0
next reply other threads:[~2025-07-05 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 7:57 Christophe JAILLET [this message]
2025-07-05 7:57 ` [PATCH 1/2] i2c: omap: Handle omap_i2c_init() errors in omap_i2c_probe() Christophe JAILLET
2025-07-09 18:25 ` Aaro Koskinen
2025-07-09 19:03 ` Andi Shyti
2025-07-18 8:20 ` Andreas Kemnade
2025-07-05 7:57 ` [PATCH 2/2] i2c: omap: Fix an error handling path " Christophe JAILLET
2025-07-18 8:17 ` Andreas Kemnade
2025-07-09 14:02 ` [PATCH 0/2] i2c: omap: 2 Fixes 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=cover.1751701715.git.christophe.jaillet@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=aaro.koskinen@iki.fi \
--cc=andi.shyti@kernel.org \
--cc=andreas@kemnade.info \
--cc=grygorii.strashko@ti.com \
--cc=jmkrzyszt@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=miaoqinglang@huawei.com \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.com \
--cc=wsa@kernel.org \
/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).