mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: vaibhavgupta40@gmail.com
Cc: helgaas@kernel.org, bhelgaas@google.com, bjorn@helgaas.com,
	kuba@kernel.org, vaibhav.varodek@gmail.com,
	linux-kernel-mentees@lists.linuxfoundation.org,
	skhan@linuxfoundation.org, netdev@vger.kernel.org,
	linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/5] ethernet: dec: tulip: use generic power management
Date: Tue, 23 Jun 2020 20:33:31 -0700 (PDT)	[thread overview]
Message-ID: <20200623.203331.577057867637454372.davem@davemloft.net> (raw)
In-Reply-To: <20200622114228.60027-1-vaibhavgupta40@gmail.com>

From: Vaibhav Gupta <vaibhavgupta40@gmail.com>
Date: Mon, 22 Jun 2020 17:12:23 +0530

> Linux Kernel Mentee: Remove Legacy Power Management.
> 
> The purpose of this patch series is to remove legacy power management
> callbacks and invocation of PCI helper functions, from tulip ethernet drivers.
> 
> With legacy PM, drivers themselves are responsible for handling the device's
> power states. And they do this with the help of PCI helper functions like
> pci_enable/disable_device(), pci_set/restore_state(), pci_set_powr_state(), etc.
> which is not recommended.
> 
> In generic PM, all the required tasks are handled by PCI core and drivers need
> to perform device-specific operations only.
> 
> All patches are compile-tested only.

Series applied to net-next, thanks.

      parent reply	other threads:[~2020-06-24  3:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 11:42 Vaibhav Gupta
2020-06-22 11:42 ` [PATCH v1 1/5] tulip: dmfe: " Vaibhav Gupta
2020-06-22 11:42 ` [PATCH v1 2/5] tulip: windbond-840: " Vaibhav Gupta
2020-06-22 11:42 ` [PATCH v1 3/5] tulip: de2104x: " Vaibhav Gupta
2020-06-22 11:42 ` [PATCH v1 4/5] tulip: tulip_core: " Vaibhav Gupta
2020-06-22 11:42 ` [PATCH v1 5/5] tulip: uli526x: " Vaibhav Gupta
2020-06-24  3:33 ` David Miller [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=20200623.203331.577057867637454372.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bhelgaas@google.com \
    --cc=bjorn@helgaas.com \
    --cc=helgaas@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=vaibhav.varodek@gmail.com \
    --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

all inboxes | Powered by JetHome®