From: Aditya Garg <gargaditya08@live.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Atharva Tiwari <evepolonium@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Jean Delvare <jdelvare@suse.com>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Orlando Chamberlain <orlandoch.dev@gmail.com>
Subject: Re: [PATCH v2] hwmom/applesmc: add imacpro
Date: Wed, 29 Jan 2025 18:22:59 +0000 [thread overview]
Message-ID: <7D2F2DB0-E94C-4372-9285-A91C4C856934@live.com> (raw)
In-Reply-To: <2346bf1d-9292-40cf-84fe-fb173baeed08@roeck-us.net>
Hi Guenter
Sorry to barge in like that but I have some issues with this here.
1. The iMacPro1,1 is a T2 Mac and the applesmc driver does not support T2 Macs upstream, thus making no point of adding this. We at t2linux have downstream patches to support T2 Macs, but we do not aim to upstream them since we wish to use a separate, and better driver for the SMC on T2 Macs.
2. The person who submitted the patch took it from the t2linux project, of which I am a part of, but didn't care to even credit the original author of the patch. I’m not sure how legal it is to redistribute the code in his own name and removing the original author’s name without taking permission from the author as per the GPL2 license, but I think the author should be credited. In fact the original patch was Signed-off-by the original author.
For reference, the original patch, which we never intended to be sent upstream, is given over here:
https://github.com/t2linux/linux-t2-patches/blob/main/3007-applesmc-Add-iMacPro-to-applesmc_whitelist.patch
I leave the fate of this to you now.
Regards
Aditya
> On 29 Jan 2025, at 9:36 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> On Thu, Jan 23, 2025 at 05:47:28PM +0530, Atharva Tiwari wrote:
>> Add iMacPro to whitelist as one iMacPro is released.
>> The iMacPro 1,1
>>
>> Signed-off-by: Atharva Tiwari <evepolonium@gmail.com>
>
> Applied to hwmon-next.
>
> Note that the branch will only be pushed to linux-next after the commit
> window closed.
>
> Thanks,
> Guenter
>
next prev parent reply other threads:[~2025-01-29 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 12:17 [PATCH v2] hwmom/applesmc: add imacpro Atharva Tiwari
2025-01-29 16:06 ` Guenter Roeck
2025-01-29 16:23 ` Guenter Roeck
2025-01-29 18:22 ` Aditya Garg [this message]
2025-01-29 19:36 ` Guenter Roeck
2025-01-30 3:54 ` Aditya Garg
2025-01-30 5:07 ` Guenter Roeck
2025-01-30 11:31 ` Aditya Garg
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=7D2F2DB0-E94C-4372-9285-A91C4C856934@live.com \
--to=gargaditya08@live.com \
--cc=evepolonium@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=orlandoch.dev@gmail.com \
--cc=rydberg@bitmath.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