From: Guenter Roeck <linux@roeck-us.net>
To: Arimil <renari@arimil.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/3] hwmon: (asus_rog_ryujin) Add per-device configuration
Date: Sun, 9 Aug 2026 15:54:52 -0700 [thread overview]
Message-ID: <28fd27da-ced5-4c2d-bbb8-0eda383bf767@roeck-us.net> (raw)
In-Reply-To: <CADBHdQ3LhfunbnwCE2AYmWr5XwqSvJ8WGkQFW1G=GQv4dp=Ndw@mail.gmail.com>
On 8/9/26 15:03, Arimil wrote:
> The github mirror that hosts the same code here:
> https://github.com/aleksamagicka/asus_rog_ryujin-hwmon
>
Sorry, you lost me. Why did you submit a patch series for inclusion
into the upstream Linux kernel if you want it to be applied to some
downstream driver on github ?
Either case, sure, go ahead, and feel free to discuss with the maintainer
of that driver if and when to submit the patches for inclusion into the
upstream Linux kernel. Going forward, please do not submit patches for
inclusion into the upstream Linux kernel if that is not what you want.
Thanks,
Guenter
next prev parent reply other threads:[~2026-08-09 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 0:01 [PATCH 0/3] hwmon: Add ASUS ROG Ryujin III support Arie Miller
2026-08-07 0:01 ` [PATCH 1/3] hwmon: (asus_rog_ryujin) Add per-device configuration Arie Miller
2026-08-07 0:14 ` sashiko-bot
2026-08-09 16:37 ` Guenter Roeck
[not found] ` <CADBHdQ3x4bFe518q2PjZvGJ2=qP45+5Cmm8f99J9gRZCJun0aQ@mail.gmail.com>
2026-08-09 20:25 ` Arimil
2026-08-09 21:23 ` Guenter Roeck
2026-08-09 22:03 ` Arimil
2026-08-09 22:54 ` Guenter Roeck [this message]
2026-08-10 1:08 ` Arimil
2026-08-10 1:19 ` Guenter Roeck
2026-08-10 1:58 ` Arimil
2026-08-07 0:01 ` [PATCH 2/3] hwmon: (asus_rog_ryujin) Add ROG Ryujin III support Arie Miller
2026-08-07 0:12 ` sashiko-bot
2026-08-07 0:01 ` [PATCH 3/3] hwmon: (asus_rog_ryujin) Add ROG Ryujin III White Edition Arie Miller
2026-08-07 0:10 ` sashiko-bot
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=28fd27da-ced5-4c2d-bbb8-0eda383bf767@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=renari@arimil.com \
/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).