From: Vaibhav Gupta <vaibhavgupta40@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <helgaas@kernel.org>,
netdev@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
"David S. Miller" <davem@davemloft.net>,
Stanislav Yakovlev <stas.yakovlev@gmail.com>
Subject: Re: [Linux-kernel-mentees] [PATCH v1 0/2] ipw2x00: use generic power management
Date: Mon, 13 Jul 2020 20:15:56 +0530 [thread overview]
Message-ID: <CAP+cEONk=XKqw4FWkBgTTaudGewJb832OjHutUpAKYpnY-uJ3A@mail.gmail.com> (raw)
In-Reply-To: <87a703xys7.fsf@codeaurora.org>
[-- Attachment #1.1: Type: text/plain, Size: 1353 bytes --]
On Mon, Jul 13, 2020, 8:12 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> Vaibhav Gupta <vaibhavgupta40@gmail.com> writes:
>
> > Linux Kernel Mentee: Remove Legacy Power Management.
> >
> > The purpose of this patch series is to remove legacy power management
> callbacks
> > from amd ethernet drivers.
> >
> > The callbacks performing suspend() and resume() operations are still
> calling
> > pci_save_state(), pci_set_power_state(), etc. and handling the power
> management
> > themselves, which is not recommended.
> >
> > The conversion requires the removal of the those function calls and
> change the
> > callback definition accordingly and make use of dev_pm_ops structure.
> >
> > All patches are compile-tested only.
> >
> > Vaibhav Gupta (2):
> > ipw2100: use generic power management
> > ipw2200: use generic power management
> >
> > drivers/net/wireless/intel/ipw2x00/ipw2100.c | 31 +++++---------------
> > drivers/net/wireless/intel/ipw2x00/ipw2200.c | 30 +++++--------------
>
> amd ethernet drivers? That must be a copy paste error. But no need to
> resend because of this.
>
Yes. I am genuinely sorry for this. My two patch-series had same changes,
so I copy-pasted the cover letter. Forgot to replace the name.
Thanks
-- Vaibhav Gupta
>
> --
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>
[-- Attachment #1.2: Type: text/html, Size: 2249 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-07-13 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 7:25 [Linux-kernel-mentees] [PATCH v1 0/2] ipw2x00: use generic power management Vaibhav Gupta
2020-06-29 7:25 ` [Linux-kernel-mentees] [PATCH v1 1/2] ipw2100: " Vaibhav Gupta
2020-07-15 10:39 ` Kalle Valo
2020-06-29 7:25 ` [Linux-kernel-mentees] [PATCH v1 2/2] ipw2200: " Vaibhav Gupta
2020-07-13 14:41 ` [Linux-kernel-mentees] [PATCH v1 0/2] ipw2x00: " Kalle Valo
2020-07-13 14:45 ` Vaibhav Gupta [this message]
2020-07-13 14:56 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2020-06-29 3:32 Vaibhav Gupta
2020-06-29 5:50 ` Kalle Valo
2020-06-29 7:13 ` Vaibhav Gupta
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='CAP+cEONk=XKqw4FWkBgTTaudGewJb832OjHutUpAKYpnY-uJ3A@mail.gmail.com' \
--to=vaibhavgupta40@gmail.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.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=stas.yakovlev@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).