From: Aleksa Savic <savicaleksa83@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: savicaleksa83@gmail.com, linux-hwmon@vger.kernel.org,
Jack Doan <me@jackdoan.com>, Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] hwmon: (aquacomputer_d5next) Add selective 200ms delay after sending ctrl report
Date: Tue, 15 Aug 2023 17:22:30 +0200 [thread overview]
Message-ID: <35cea1ae-df13-6309-1b00-6ee236118143@gmail.com> (raw)
In-Reply-To: <b1083bf1-9d28-48f3-a984-38f63ec1fd16@roeck-us.net>
On 2023-08-14 15:42:19 GMT+02:00, Guenter Roeck wrote:
> On Sat, Aug 12, 2023 at 08:49:49PM +0200, Aleksa Savic wrote:
>> On 2023-08-12 01:05:19 GMT+02:00, Guenter Roeck wrote:
>>>
>>> It has a Fixes: tag, so it will be applied to affected stable releases
>>> automatically, at least if it applies cleanly. I could have added Cc:
>>> stable@ to make it explicit, but I had pushed it already, and I didn't
>>> want to rebase the branch just for that.
>>>
>>> Guenter
>>>
>>
>> Didn't know explicit Cc wasn't necessary, thanks.
>>
>
> Preferred but not necessary. You should have received an e-mail telling
> you that the patch did not apply to 6.1.y. If you want it applied there,
> send a backport to stable@ with a subject such as [PATCH v6.1] ...
> and backport comments after "---".
>
> Guenter
Thanks, will do.
Aleksa
prev parent reply other threads:[~2023-08-15 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:20 Aleksa Savic
2023-08-10 4:09 ` Guenter Roeck
2023-08-10 18:15 ` Aleksa Savic
2023-08-11 23:05 ` Guenter Roeck
2023-08-12 18:49 ` Aleksa Savic
2023-08-14 13:42 ` Guenter Roeck
2023-08-15 15:22 ` Aleksa Savic [this message]
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=35cea1ae-df13-6309-1b00-6ee236118143@gmail.com \
--to=savicaleksa83@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=me@jackdoan.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
all inboxes | Powered by JetHome®