From: Vaibhav Gupta <vaibhav.varodek@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Vaibhav Gupta <vaibhavgupta40@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org, Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
bjorn@helgaas.com,
linux-kernel-mentees@lists.linuxfoundation.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH net-next v3 0/2] realtek ethernet : use generic power management.
Date: Wed, 24 Jun 2020 22:01:06 +0530 [thread overview]
Message-ID: <CAPBsFfBhWAYCuxWxP=DnD1Ja5cQ44i5guRC+49gAHsTxJV25qw@mail.gmail.com> (raw)
In-Reply-To: <20200519.153239.1577517664546707472.davem@davemloft.net>
On Wed, 20 May 2020 at 04:02, David Miller <davem@davemloft.net> wrote:
>
> From: Vaibhav Gupta <vaibhavgupta40@gmail.com>
> Date: Mon, 18 May 2020 20:32:12 +0530
>
> > The purpose of this patch series is to remove legacy power management callbacks
> > from realtek ethernet drivers.
> >
> > The callbacks performing suspend() and resume() operations are still calling
> > pci_save_state(), pci_set_power_state(), etc. and handling the powermanagement
> > themselves, which is not recommended.
> >
> > The conversion requires the removal of the those function calls and change the
> > callback definition accordingly.
> >
> > All Changes are compile-tested only.
>
> Series applied
Thanks !
-- Vaibhav Gupta
> , thanks.
prev parent reply other threads:[~2020-06-24 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 15:02 [PATCH net-next v3 0/2] realtek ethernet : use generic power management Vaibhav Gupta
2020-05-18 15:02 ` [PATCH net-next v3 1/2] realtek/8139too: " Vaibhav Gupta
2020-05-18 15:02 ` [PATCH net-next v3 2/2] realtek/8139cp: " Vaibhav Gupta
2020-05-19 22:32 ` [PATCH net-next v3 0/2] realtek ethernet : " David Miller
2020-06-24 16:31 ` Vaibhav Gupta [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='CAPBsFfBhWAYCuxWxP=DnD1Ja5cQ44i5guRC+49gAHsTxJV25qw@mail.gmail.com' \
--to=vaibhav.varodek@gmail.com \
--cc=bhelgaas@google.com \
--cc=bjorn@helgaas.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=skhan@linuxfoundation.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).