From: Lee Jones <lee.jones@linaro.org>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Martin Petersen <martin.petersen@oracle.com>,
SCSI <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Evan Green <evgreen@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
Joao Pinto <jpinto@synopsys.com>, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Bart Van Assche <bart.vanassche@wdc.com>,
Stanislav Nijnikov <stanislav.nijnikov@wdc.com>,
Alex Lemberg <alex.lemberg@wdc.com>,
Ohad Sharabi <ohad.sharabi@wdc.com>,
Venkat Gopalakrishnan <venkatg@codeaurora.org>
Subject: Re: [PATCH v5 0/2] Clean up UFSHC driver
Date: Tue, 26 Feb 2019 08:57:30 +0000 [thread overview]
Message-ID: <20190226085730.GK4118@dell> (raw)
In-Reply-To: <60e5da74-da0d-4ba7-6d29-2ca6008b6ceb@free.fr>
On Sat, 23 Feb 2019, Marc Gonzalez wrote:
> Martin,
>
> Could you send this series to -next so that it gets some exposure
> and testing during the 5.1 RC cycle?
Replying for the purpose of providing some gravitas to this set.
These patches are required to support some exciting consumer hardware
which has been recently released [0][1][2][3][4]. If they do not
find their way into Mainline very soon, it would mean that supporting
these devices in the most popular Linux distos will be difficult to
impossible.
Please consider them for the v5.1 merge window which opens in a week.
[0] https://joindiaspora.com/posts/4714199011120137995e0218b7b935a5
[1] https://liliputing.com/2019/02/now-you-can-run-linux-on-some-arm-laptops-designed-for-windows-10-on-arm.html
[2] https://www.phoronix.com/scan.php?page=news_item&px=Linux-On-The-Win-Arm-Laptops
[3] https://fossbytes.com/linux-on-windows-10-arm-laptops-project/
[4] https://www.techrepublic.com/article/open-source-project-aims-to-make-ubuntu-usable-on-arm-powered-windows-laptops/
> On 11/02/2019 14:31, Marc Gonzalez wrote:
>
> > Casting a wide net to get as many eyeballs on the subject as possible.
> >
> > I'm splitting this mini series off from the main "UFS on APQ8098/MSM8998"
> > as it's 1) ufs/scsi specific 2) controversial (to my surprise)
> >
> > Please send all your Reviewed-by: tags if you agree with the patch,
> > and/or voice your concerns ASAP.
> >
> > This series removes the "disable-VCCQ-power-rail-for-some-Flash-chips" quirk,
> > and cleans up after the dust settles.
> >
> > Marc Gonzalez (2):
> > scsi: ufs: Do not disable vccq in UFSHC driver
> > scsi: ufs: Remove unused device quirks
> >
> > drivers/scsi/ufs/ufs.h | 1 -
> > drivers/scsi/ufs/ufs_quirks.h | 29 ----------------
> > drivers/scsi/ufs/ufshcd.c | 63 +++--------------------------------
> > 3 files changed, 4 insertions(+), 89 deletions(-)
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-02-26 8:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190211133457epcas3p2dc95fa2c93c3cf884a376f0282be8b8a@epcas3p2.samsung.com>
2019-02-11 13:31 ` [PATCH v5 0/2] Clean up UFSHC driver Marc Gonzalez
2019-02-11 13:32 ` [PATCH v5 1/2] scsi: ufs: Do not disable vccq in " Marc Gonzalez
2019-02-11 17:23 ` Mark Brown
2019-02-13 10:05 ` Marc Gonzalez
2019-02-26 9:05 ` Avri Altman
2019-02-26 14:44 ` Martin K. Petersen
2019-02-26 14:45 ` Marc Gonzalez
2019-02-26 14:52 ` Martin K. Petersen
2019-02-26 15:30 ` Marc Gonzalez
2019-02-26 16:26 ` Martin K. Petersen
2019-02-26 17:02 ` Marc Gonzalez
2019-02-26 20:00 ` Martin K. Petersen
2019-02-11 13:33 ` [PATCH v5 2/2] scsi: ufs: Remove unused device quirks Marc Gonzalez
2019-02-26 9:05 ` Avri Altman
2019-02-26 17:14 ` Evan Green
2019-02-13 10:25 ` [PATCH v5 0/2] Clean up UFSHC driver Alim Akhtar
2019-02-23 9:39 ` Marc Gonzalez
2019-02-26 8:57 ` Lee Jones [this message]
2019-02-27 10:38 Marc Gonzalez
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=20190226085730.GK4118@dell \
--to=lee.jones@linaro.org \
--cc=alex.lemberg@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bart.vanassche@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=jhugo@codeaurora.org \
--cc=jpinto@synopsys.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=martin.petersen@oracle.com \
--cc=ohad.sharabi@wdc.com \
--cc=pedrom.sousa@synopsys.com \
--cc=robh+dt@kernel.org \
--cc=stanislav.nijnikov@wdc.com \
--cc=venkatg@codeaurora.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