linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Arnd Bergmann <arnd.bergmann@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Maximilian Luz <luzmaximilian@gmail.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH -next] platform: surface: fix non-PM_SLEEP build warnings
Date: Mon, 14 Dec 2020 15:49:33 -0800	[thread overview]
Message-ID: <0f07d6b8-6a28-ba31-9cfa-53abffb0c0ff@infradead.org> (raw)
In-Reply-To: <CAHp75Vc3_ye3Ph0uVYdcsKr0QY5RGSaHmCgU1A2q-U2GCAafsQ@mail.gmail.com>

On 12/14/20 3:19 AM, Andy Shevchenko wrote:
> On Mon, Dec 14, 2020 at 2:53 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 12/12/20 11:07 AM, Andy Shevchenko wrote:
>>> On Sat, Dec 12, 2020 at 7:05 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> ...
> 
>>> Here [1] is the rationale behind annotation vs. ifdeffery.
>>>
>>> [1]: https://lore.kernel.org/patchwork/patch/732981/
>>>
>> Thanks for the link.  I'll send a v2.
>>
>> Could we add that to the Linux BKP (Best Known Practices)
>> document?
> 
> Perhaps. The author of that is Arnd, maybe he has something to add.
> 

Where is it located?  My search foo could not find it.

thanks.
-- 
~Randy

  reply	other threads:[~2020-12-14 23:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 19:03 [PATCH -next] platform: surface: fix non-PM_SLEEP build warnings Randy Dunlap
2020-12-11 20:23 ` Maximilian Luz
2020-12-11 20:41   ` Randy Dunlap
2020-12-11 21:00     ` Maximilian Luz
2020-12-12 13:24 ` Andy Shevchenko
2020-12-12 17:05   ` Randy Dunlap
2020-12-12 19:07     ` Andy Shevchenko
2020-12-14  0:53       ` Randy Dunlap
2020-12-14 11:19         ` Andy Shevchenko
2020-12-14 23:49           ` Randy Dunlap [this message]
2020-12-16 10:49             ` Andy Shevchenko

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=0f07d6b8-6a28-ba31-9cfa-53abffb0c0ff@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd.bergmann@linaro.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=platform-driver-x86@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).