linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Vaibhav Gupta <vaibhavgupta40@gmail.com>
Cc: Vaibhav Gupta <vaibhavgupta40@gmail.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Bjorn Helgaas <helgaas@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kernel-mentees@lists.linuxfoundation.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Linux-kernel-mentees] [PATCH v1] rtl818x_pci: use generic power management
Date: Wed, 15 Jul 2020 10:38:15 +0000 (UTC)	[thread overview]
Message-ID: <20200715103815.165DAC433A0@smtp.codeaurora.org> (raw)
In-Reply-To: <20200623094454.12427-1-vaibhavgupta40@gmail.com>

Vaibhav Gupta <vaibhavgupta40@gmail.com> wrote:

> Earlier, drivers had to manage the device's power states, and related
> operations, themselves. With the generic approach, these are done by PCI
> core.
> 
> The only driver-specific jobs, .suspend() and .resume() doing were invoking
> PCI helper functions pci_save/restore_state() and
> pci_set_power_state(). This is not recommeneded as PCI core takes care of
> that. Hence they became empty-body functions, thus define them NULL.
> 
> Compile-tested only.
> 
> Signed-off-by: Vaibhav Gupta <vaibhavgupta40@gmail.com>

Patch applied to wireless-drivers-next.git, thanks.

ef6425107ccc rtl818x_pci: use generic power management

-- 
https://patchwork.kernel.org/patch/11620213/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

      reply	other threads:[~2020-07-15 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  9:44 [Linux-kernel-mentees] [PATCH v1] rtl818x_pci: use generic power management Vaibhav Gupta
2020-07-15 10:38 ` Kalle Valo [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=20200715103815.165DAC433A0@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=helgaas@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vaibhavgupta40@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 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).