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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 6 Oct 2015 17:02:00 +0200
From:	Javier Martinez Canillas <>
To:	Kishon Vijay Abraham I <>,
	Marek Szyprowski <>,
	Krzysztof Kozlowski <>
Subject: Re: [PATCH RESEND] phy: exynos-usb2: add vbus regulator support

Hello Kishon,

On 10/06/2015 04:29 PM, Kishon Vijay Abraham I wrote:
> On Tuesday 06 October 2015 07:39 PM, Marek Szyprowski wrote:


>> This was a pure resend, no changes to the patch has been made. I just
>> noticed
>> that it is over 6 weeks since the initial submission and the patch is still
>> not in linux-next...
> It won't be in linux-next. I've just merged this patch to linux-phy
> -next and will be sent during the next merge window. Only fixes will be
> merged during the -rc releases.

When patches are pushed to mainline it's somehow orthogonal to what is
exposed in -next. Only fixes for regressions will be pushed during the
-rc cycle and new features will be pushed during the next merge window
of course but that should not prevent accepted patches to get some test
coverage under -next.

In fact, ideally patches should sit in -next for a couple of weeks before
are pushed to mainline since there is a lot of automated (0day, kernelci,
etc) and manual testing that happen on that tree to detect issues earlier.

I noticed that linux-phy isn't shown in [0] though, probably should be added?

> Thanks
> Kishon
> --


Best regards,
Javier Martinez Canillas
Open Source Group
Samsung Research America
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists