From: Anna-Maria Behnsen <anna-maria@linutronix•de>
To: Mark Brown <broonie@kernel•org>,
Frederic Weisbecker <frederic@kernel•org>,
Thomas Gleixner <tglx@linutronix•de>,
Jonathan Corbet <corbet@lwn•net>
Cc: linux-kernel@vger•kernel.org, Len Brown <len.brown@intel•com>,
"Rafael J. Wysocki" <rafael@kernel•org>,
rust-for-linux@vger•kernel.org, Alice Ryhl <aliceryhl@google•com>,
FUJITA Tomonori <fujita.tomonori@gmail•com>,
Andrew Lunn <andrew@lunn•ch>, Miguel Ojeda <ojeda@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>,
damon@lists•linux.dev, linux-mm@kvack•org,
SeongJae Park <sj@kernel•org>, Arnd Bergmann <arnd@arndb•de>,
linux-arch@vger•kernel.org,
Heiner Kallweit <hkallweit1@gmail•com>,
"David S. Miller" <davem@davemloft•net>,
Andy Whitcroft <apw@canonical•com>, Joe Perches <joe@perches•com>,
Dwaipayan Ray <dwaipayanray1@gmail•com>,
Liam Girdwood <lgirdwood@gmail•com>,
Jaroslav Kysela <perex@perex•cz>, Takashi Iwai <tiwai@suse•com>,
netdev@vger•kernel.org, linux-sound@vger•kernel.org,
Michael Ellerman <mpe@ellerman•id.au>,
Nathan Lynch <nathanl@linux•ibm.com>,
linuxppc-dev@lists•ozlabs.org,
Mauro Carvalho Chehab <mchehab@kernel•org>,
linux-media@vger•kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix•de>
Subject: Re: (subset) [PATCH v3 00/16] timers: Cleanup delay/sleep related mess
Date: Fri, 18 Oct 2024 10:06:33 +0200 [thread overview]
Message-ID: <877ca5al86.fsf@somnus> (raw)
In-Reply-To: <172892295715.1548.770734377772758528.b4-ty@kernel.org>
Hi Mark,
Mark Brown <broonie@kernel•org> writes:
> On Mon, 14 Oct 2024 10:22:17 +0200, Anna-Maria Behnsen wrote:
>> a question about which sleeping function should be used in acpi_os_sleep()
>> started a discussion and examination about the existing documentation and
>> implementation of functions which insert a sleep/delay.
>>
>> The result of the discussion was, that the documentation is outdated and
>> the implemented fsleep() reflects the outdated documentation but doesn't
>> help to reflect reality which in turns leads to the queue which covers the
>> following things:
>>
>> [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
>
Would it be ok for you, if the patch is routed through tip tree? kernel
test robot triggers a warning for htmldoc that there is a reference to
the no longer existing file 'timer-howto.rst':
https://lore.kernel.org/r/202410161059.a0f6IBwj-lkp@intel.com
Thanks,
Anna-Maria
next prev parent reply other threads:[~2024-10-18 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 8:22 [PATCH v3 00/16] timers: Cleanup delay/sleep related mess Anna-Maria Behnsen
2024-10-14 8:22 ` [PATCH v3 12/16] iopoll/regmap/phy/snd: Fix comment referencing outdated timer documentation Anna-Maria Behnsen
2024-10-14 16:22 ` (subset) [PATCH v3 00/16] timers: Cleanup delay/sleep related mess Mark Brown
2024-10-18 8:06 ` Anna-Maria Behnsen [this message]
2024-10-18 18:57 ` Mark Brown
2024-10-18 18:58 ` Mark Brown
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=877ca5al86.fsf@somnus \
--to=anna-maria@linutronix$(echo .)de \
--cc=akpm@linux-foundation$(echo .)org \
--cc=aliceryhl@google$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=apw@canonical$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=bigeasy@linutronix$(echo .)de \
--cc=broonie@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=damon@lists$(echo .)linux.dev \
--cc=davem@davemloft$(echo .)net \
--cc=dwaipayanray1@gmail$(echo .)com \
--cc=frederic@kernel$(echo .)org \
--cc=fujita.tomonori@gmail$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=joe@perches$(echo .)com \
--cc=len.brown@intel$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-sound@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mchehab@kernel$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=nathanl@linux$(echo .)ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ojeda@kernel$(echo .)org \
--cc=perex@perex$(echo .)cz \
--cc=rafael@kernel$(echo .)org \
--cc=rust-for-linux@vger$(echo .)kernel.org \
--cc=sj@kernel$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=tiwai@suse$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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