From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH 6/8] header: add pm_system_wakeup()
Date: Tue, 12 Sep 2017 11:35:53 +0200 [thread overview]
Message-ID: <1505208953.1974.5.camel@sipsolutions.net> (raw)
In-Reply-To: <20170910221020.13067-7-hauke@hauke-m.de> (sfid-20170911_001052_010594_5AEDB503)
On Mon, 2017-09-11 at 00:10 +0200, Hauke Mehrtens wrote:
>
> +#if LINUX_VERSION_IS_LESS(3,18,0)
> +static inline void pm_system_wakeup(void)
> +{
> + freeze_wake();
> +}
> +#endif
freeze_wake() was also "only" added around 3.10 or something like that,
so perhaps we should just not backport this at all but version-guard
the drivers needing it? I'm not super comfortable with the reduced
functionality anyway.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-09-12 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 22:10 [PATCH 0/8] backports: misc fixes Hauke Mehrtens
2017-09-10 22:10 ` [PATCH 1/8] patches: export bp_usbnet_get_stats64() only if function is added Hauke Mehrtens
2017-09-10 22:10 ` [PATCH 2/8] patches: brcmfmac: Fix netdev_set_priv_destructor Hauke Mehrtens
2017-09-10 22:10 ` [PATCH 3/8] backport: add ethtool_convert_legacy_u32_to_link_mode() Hauke Mehrtens
2017-09-10 22:10 ` [PATCH 4/8] header: add IOMEM_ERR_PTR() Hauke Mehrtens
2017-09-10 22:10 ` [PATCH 5/8] header: add __get_dynamic_array_len Hauke Mehrtens
2017-09-10 22:10 ` [PATCH 6/8] header: add pm_system_wakeup() Hauke Mehrtens
2017-09-12 9:35 ` Johannes Berg [this message]
2017-09-12 21:39 ` Hauke Mehrtens
2017-09-15 7:32 ` Johannes Berg
2017-09-10 22:10 ` [PATCH 7/8] dependencies: make NFC_TRF7970A depend on kernel > 3.17 Hauke Mehrtens
2017-09-10 22:10 ` [PATCH 8/8] dependencies: make MWIFIEX_PCIE depend on kernel > 3.16 Hauke Mehrtens
2017-09-11 14:48 ` [PATCH 0/8] backports: misc fixes Johannes Berg
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=1505208953.1974.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
/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.