From: Guenter Roeck <linux@roeck-us.net>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
openbmc@lists.ozlabs.org,
Jaghathiswari Rankappagounder Natarajan <jaghu@google.com>
Subject: Re: [PATCH] hwmon: (aspeed-pwm-tacho): Add dependency on ARCH_ASPEED
Date: Mon, 19 Sep 2022 06:13:05 -0700 [thread overview]
Message-ID: <20220919131305.GA3545921@roeck-us.net> (raw)
In-Reply-To: <20220916120936.372591-1-pbrobinson@gmail.com>
On Fri, Sep 16, 2022 at 01:09:36PM +0100, Peter Robinson wrote:
> The SENSORS_ASPEED is part of the Aspeed silicon so it makes
> sense to depend on ARCH_ASPEED and for compile testing.
>
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Applied.
Thanks,
Guenter
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: linux-hwmon@vger.kernel.org,
Jaghathiswari Rankappagounder Natarajan <jaghu@google.com>,
openbmc@lists.ozlabs.org, Jean Delvare <jdelvare@suse.com>,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH] hwmon: (aspeed-pwm-tacho): Add dependency on ARCH_ASPEED
Date: Mon, 19 Sep 2022 06:13:05 -0700 [thread overview]
Message-ID: <20220919131305.GA3545921@roeck-us.net> (raw)
In-Reply-To: <20220916120936.372591-1-pbrobinson@gmail.com>
On Fri, Sep 16, 2022 at 01:09:36PM +0100, Peter Robinson wrote:
> The SENSORS_ASPEED is part of the Aspeed silicon so it makes
> sense to depend on ARCH_ASPEED and for compile testing.
>
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Applied.
Thanks,
Guenter
next prev parent reply other threads:[~2022-09-19 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 12:09 [PATCH] hwmon: (aspeed-pwm-tacho): Add dependency on ARCH_ASPEED Peter Robinson
2022-09-19 13:13 ` Guenter Roeck [this message]
2022-09-19 13:13 ` 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=20220919131305.GA3545921@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jaghu@google.com \
--cc=jdelvare@suse.com \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pbrobinson@gmail.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 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.