From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH RESEND] phy: exynos-usb2: add vbus regulator support
Date: Tue, 6 Oct 2015 17:02:00 +0200 [thread overview]
Message-ID: <5613E268.30508@osg.samsung.com> (raw)
In-Reply-To: <5613DAC2.7050508@ti.com>
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:
[snip]
>>
>> 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
> --
[0]: http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Next/Trees?id=HEAD
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
prev parent reply other threads:[~2015-10-06 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 13:41 [PATCH RESEND] phy: exynos-usb2: add vbus regulator support Marek Szyprowski
2015-10-06 13:47 ` Krzysztof Kozlowski
2015-10-06 14:09 ` Marek Szyprowski
2015-10-06 14:29 ` Kishon Vijay Abraham I
2015-10-06 15:02 ` Javier Martinez Canillas [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=5613E268.30508@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.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