linux-kernel - Re: UFS V11 patch-set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Mar 2016 15:39:54 +0000
From:	Joao Pinto <Joao.Pinto@...opsys.com>
To:	Mark Brown <broonie@...nel.org>,
	Joao Pinto <Joao.Pinto@...opsys.com>
CC:	vinayak holikatti <vinholikatti@...il.com>,
	<JBottomley@...allels.com>, <rafael.j.wysocki@...el.com>,
	<hch@....de>, Arnd Bergmann <arnd@...db.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Carlos Palminha" <CARLOS.PALMINHA@...opsys.com>,
	<gregkh@...uxfoundation.org>,
	"robh@...nel.org >> Rob Herring" <robh@...nel.org>
Subject: Re: UFS V11 patch-set

On 3/22/2016 3:31 PM, Mark Brown wrote:
> On Tue, Mar 22, 2016 at 11:04:25AM +0000, Joao Pinto wrote:
> 
> Please don't top post, reply in line with needed context.  This allows
> readers to readily follow the flow of conversation and understand what
> you are talking about and also helps ensure that everything in the
> discussion is being addressed.
> 
>> I have no intend to break the rules. I am just trying to communicate with UFS
>> maintainers that so far gave me no response. Merging in v4.7 is fine, but I
>> would like that UFS maintainers give me some feedback about the next steps, but
>> so far didn't have luck.
> 
> Like I say the next steps are those Arnd gave you: repost after -rc1.
> Then give people at least a week or so to respond, people do get busy
> and other people are also sending patches.
> 

Understood, I will repost this patch set after -rc1.
I suggest that the UFS maintenance should be revised because the e-mail of
ufshcd.c authors are no longer valid and the current maintainer (Vinayak
Holikatti) is having a career shift (has you can check in LinkedIn) and probably
is not available at the moment to do patch reviews.

Thanks,
Joao