From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: <Shirley.Lin@infineon.com>, <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>
Cc: <Mills.Liu@infineon.com>, <Ashish.Yadav@infineon.com>,
<Ian.Fang@infineon.com>
Subject: Re: Update driver xdpe152c4.c
Date: Mon, 7 Apr 2025 10:29:17 +0530 [thread overview]
Message-ID: <eeef6c60-8de2-4a4d-8bc5-2c321d759672@quicinc.com> (raw)
In-Reply-To: <3f7d0644a1f844b8b3ee9b3139b85339@infineon.com>
On 4/7/2025 9:22 AM, Shirley.Lin@infineon.com wrote:
> Dear Linux Kernel administrators, Good Day.
>
> We have urgent requirement to update driver link, https://github.com/
> torvalds/linux/blob/master/drivers/hwmon/pmbus/xdpe152c4.c <https://
> github.com/torvalds/linux/blob/master/drivers/hwmon/pmbus/xdpe152c4.c#L72>
>
> Please help to reviewthe attached Linux Kernel patch for xdpe152xx driver.
>
This is not the way to upstream from your side and get it reviewed by
others.
please follow standard upstream process. Review others drivers the way
it's uploaded first time and then raise new patch.
https://www.kernel.org/doc/html/v4.10/process/submitting-drivers.html
https://www.kernel.org/doc/html/v4.10/process/howto.html
> PEC Retry Functionality added for both read_word_data()
> & read_byte_data() cases of PMBUS.
>
> Updated by : Yadav Ashish (PSS PCS RD FW HD) Ashish.Yadav@infineon.com
> <mailto:Ashish.Yadav@infineon.com>
>
> Kindly leave your comment or give us approval for upstream.
>
> Thanks a lot.
>
> Best Regards,
>
> *Shirley Lin*
>
> *Infineon Technologies Taiwan Co. Ltd.*
>
> Field Application Engineer
>
> IFTW PSS SMD GC TM DCO
>
> Office: +886 2 2652 6866
>
> Mobile: +886 9 7822 9671
>
> Shirley.Lin@infineon.com <mailto:Shirley.Lin@infineon.com>
>
> 17F, No. 335, Ruiguang Road
>
> Neihu District, Taipei 114063
>
> Taiwan
>
> www.infineon.com <http://www.infineon.com/> Discoveries <http://
> www.infineon.com/discoveries> Facebook <http://www.facebook.com/
> infineon> X <https://x.com/Infineon> LinkedIn <http://www.linkedin.com/
> company/infineon-technologies>
>
next prev parent reply other threads:[~2025-04-07 4:59 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 [this message]
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
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=eeef6c60-8de2-4a4d-8bc5-2c321d759672@quicinc.com \
--to=quic_msavaliy@quicinc.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