From: Andreas Kemnade <andreas@kemnade.info>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Discussions about the Letux Kernel <letux-kernel@openphoenux.org>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel@pyra-handheld.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexios Zavras <alexios.zavras@intel.com>,
Rob Herring <robh+dt@kernel.org>,
netdev@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Letux-kernel] [PATCH 0/2] net: wireless: ti: wl1251: sdio: remove ti, power-gpio
Date: Tue, 26 Nov 2019 18:42:42 +0100 [thread overview]
Message-ID: <20191126184242.365603a2@aktux> (raw)
In-Reply-To: <0101016ea8691109-5beadf07-b3ba-4d31-a516-c7f3015f2316-000000@us-west-2.amazonses.com>
On Tue, 26 Nov 2019 15:51:28 +0000
Kalle Valo <kvalo@codeaurora.org> wrote:
> "H. Nikolaus Schaller" <hns@goldelico.com> writes:
>
> > The driver has been updated to use the mmc/sdio core
> > which does full power control. So we do no longer need
> > the power control gipo.
> >
> > Note that it is still needed for the SPI based interface
> > (N900).
> >
> > Suggested by: Ulf Hansson <ulf.hansson@linaro.org>
> > Tested by: H. Nikolaus Schaller <hns@goldelico.com> # OpenPandora 600MHz
> >
> > H. Nikolaus Schaller (2):
> > DTS: bindings: wl1251: mark ti,power-gpio as optional
> > net: wireless: ti: wl1251: sdio: remove ti,power-gpio
> >
> > .../bindings/net/wireless/ti,wl1251.txt | 3 +-
> > drivers/net/wireless/ti/wl1251/sdio.c | 30 -------------------
> > 2 files changed, 2 insertions(+), 31 deletions(-)
>
> Via which tree are these planned to go? Please always document that in
> the cover letter so that maintainers don't need to guess.
>
Hmm, this is about bisect issues and the former misc pandora
fix/cleanup series now in linux-next that make you doubt it should go
via wireless/net?
So the question is whether it depends on that?
Regards,
Andreas
prev parent reply other threads:[~2019-11-26 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 10:35 [PATCH 0/2] net: wireless: ti: wl1251: sdio: remove ti,power-gpio H. Nikolaus Schaller
2019-11-24 10:35 ` [PATCH 1/2] DTS: bindings: wl1251: mark ti,power-gpio as optional H. Nikolaus Schaller
2019-12-05 16:51 ` Rob Herring
2019-11-24 10:35 ` [PATCH 2/2] net: wireless: ti: wl1251: sdio: remove ti,power-gpio H. Nikolaus Schaller
2019-11-24 10:47 ` H. Nikolaus Schaller
2019-11-26 15:53 ` Kalle Valo
[not found] ` <0101016ea86aaa23-4980977b-7718-4ce8-9089-ae7936f60eee-000000@us-west-2.amazonses.com>
2019-11-26 16:35 ` H. Nikolaus Schaller
2019-11-26 15:51 ` [PATCH 0/2] " Kalle Valo
[not found] ` <0101016ea86910ca-f8c93455-c4de-4906-a10a-bba6be6ff35a-000000@us-west-2.amazonses.com>
2019-11-26 16:34 ` H. Nikolaus Schaller
[not found] ` <0101016ea8691109-5beadf07-b3ba-4d31-a516-c7f3015f2316-000000@us-west-2.amazonses.com>
2019-11-26 17:42 ` Andreas Kemnade [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=20191126184242.365603a2@aktux \
--to=andreas@kemnade.info \
--cc=alexios.zavras@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hns@goldelico.com \
--cc=kernel@pyra-handheld.com \
--cc=kvalo@codeaurora.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.org \
/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).