devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Shirley.Lin@infineon.com
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	jdelvare@suse.com, linux@roeck-us.net, corbet@lwn.net,
	patrick.rudolph@9elements.com, bhelgaas@google.com,
	ninad@linux.ibm.com, festevam@denx.de,
	devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-i2c@vger.kernel.org, Mills.Liu@infineon.com,
	Ashish.Yadav@infineon.com, Ian.Fang@infineon.com
Subject: Re: Update driver xdpe152c4.c
Date: Mon, 7 Apr 2025 08:15:21 +0200	[thread overview]
Message-ID: <Z_NteUAIeuDdDPls@shikoro> (raw)
In-Reply-To: <3f7d0644a1f844b8b3ee9b3139b85339@infineon.com>

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


> Please help to review the attached Linux Kernel patch for xdpe152xx driver.

To shorten things, you could return -EAGAIN as an error code, then the
I2C core will retry the message for you. Within the configured limits
for the controller.


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

  parent reply	other threads:[~2025-04-07  6:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  3:52 Update driver xdpe152c4.c Shirley.Lin
2025-04-07  4:59 ` Mukesh Kumar Savaliya
2025-04-07  6:12   ` Wolfram Sang
2025-04-07  6:58     ` Mukesh Kumar Savaliya
2025-04-07  7:23       ` Shirley.Lin
2025-04-07  6:15 ` Wolfram Sang [this message]
2025-04-07 14:01   ` Guenter Roeck
2025-04-07 14:36     ` Guenter Roeck
2025-04-08  3:28       ` Ashish.Yadav
2025-04-08  4:06         ` Guenter Roeck

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=Z_NteUAIeuDdDPls@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=Ashish.Yadav@infineon.com \
    --cc=Ian.Fang@infineon.com \
    --cc=Mills.Liu@infineon.com \
    --cc=Shirley.Lin@infineon.com \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@denx.de \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=ninad@linux.ibm.com \
    --cc=patrick.rudolph@9elements.com \
    --cc=robh@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).