From: Jaehoon Chung <jh80.chung@samsung.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>, u-boot@lists.denx.de
Cc: Marek Vasut <marex@denx.de>, Fabio Estevam <festevam@denx.de>,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 2/2] pmic: pca9450: drop pointless .data entries
Date: Tue, 14 Jun 2022 11:12:27 +0900 [thread overview]
Message-ID: <15ee5a26-5b70-1a13-418e-20473c277697@samsung.com> (raw)
In-Reply-To: <d78b75ac-6ddc-7504-2d15-02b7be5d7b0a@prevas.dk>
On 6/2/22 21:30, Rasmus Villemoes wrote:
> On 02/06/2022 02.30, Jaehoon Chung wrote:
>> Dear Rasums,
>>
>> On 5/17/22 08:44, Jaehoon Chung wrote:
>>> On 5/3/22 17:58, Rasmus Villemoes wrote:
>>>> These are the i2c addresses of the chips, but that comes from device
>>>> tree. Having that information duplicated here just adds confusion.
>>>>
>>>> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
>>
>> There is a conflict with commit 326337fb005f968911d897867d09d1228b070d84.
>> Could you send the patch again? Sorry for too late.
>
> Oh, but that commit repurposes the .data member - or rather, "purposes",
> but I don't think that's a real verb. Previously the driver_data wasn't
> used for anything, but it is now.
>
> So my patch should simply be dropped.
Okay. Thanks!
Best Regards,
Jaehoon Chung
>
> Rasmus
>
next prev parent reply other threads:[~2022-06-14 2:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220503085824epcas1p2f63014c42ef5a15cfba9eb8930a5a99c@epcas1p2.samsung.com>
2022-05-03 8:58 ` [PATCH 1/2] pmic: pca9450: add DM_I2C dependencies in Kconfig Rasmus Villemoes
2022-05-03 8:58 ` [PATCH 2/2] pmic: pca9450: drop pointless .data entries Rasmus Villemoes
2022-05-16 23:44 ` Jaehoon Chung
2022-06-02 0:30 ` Jaehoon Chung
2022-06-02 12:30 ` Rasmus Villemoes
2022-06-14 2:12 ` Jaehoon Chung [this message]
2022-05-16 23:44 ` [PATCH 1/2] pmic: pca9450: add DM_I2C dependencies in Kconfig Jaehoon Chung
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=15ee5a26-5b70-1a13-418e-20473c277697@samsung.com \
--to=jh80.chung@samsung.com \
--cc=festevam@denx.de \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=u-boot@lists.denx.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 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.