From: Javier Martinez Canillas <javier@osg.samsung.com> To: Krzysztof Kozlowski <k.kozlowski@samsung.com>, linux-kernel@vger.kernel.org Cc: Kukjin Kim <kgene@kernel.org>, Thierry Reding <treding@nvidia.com>, Geert Uytterhoeven <geert+renesas@glider.be>, Arnd Bergmann <arnd@arndb.de>, Alexandre Belloni <alexandre.belloni@free-electrons.com>, Sjoerd Simons <sjoerd.simons@collabora.co.uk>, Lee Jones <lee.jones@linaro.org>, Olof Johansson <olof@lixom.net>, Russell King <linux@armlinux.org.uk>, linux-arm-kernel@lists.infradead.org, Simon Horman <horms+renesas@verge.net.au> Subject: Re: [PATCH 2/2] ARM: multi_v7_defconfig: Enable Exynos MFC driver as module Date: Wed, 11 May 2016 08:14:51 -0400 [thread overview] Message-ID: <d36b1ca3-413a-8a19-ad96-0775593e4337@osg.samsung.com> (raw) In-Reply-To: <5732D0BF.3020207@samsung.com> Hello Krzysztof, On 05/11/2016 02:27 AM, Krzysztof Kozlowski wrote: > On 05/10/2016 11:07 PM, Javier Martinez Canillas wrote: >> Exynos SoCs have a Multi Format Video Hardware Codec (MFC) IP block that >> can be used to {en,de}code video streams by hardware. Enable support for >> its driver as a module so the MFC can be tested. >> >> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> >> >> --- >> >> This patch depends on https://patchwork.kernel.org/patch/8970711/ >> >> arch/arm/configs/multi_v7_defconfig | 1 + >> 1 file changed, 1 insertion(+) > > > Both patches look good but only exynos_defconfig ended in Patchwork. > This one did not... because you forgot to Cc the samsung-soc list. > Sigh, this time I used the cc list suggested by get_maintainers.pl and forgot to double check if was complete. I'll resend and cc samsung-soc. > Best regards, > Krzysztod > Best regards, -- Javier Martinez Canillas Open Source Group Samsung Research America
WARNING: multiple messages have this Message-ID (diff)
From: javier@osg.samsung.com (Javier Martinez Canillas) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/2] ARM: multi_v7_defconfig: Enable Exynos MFC driver as module Date: Wed, 11 May 2016 08:14:51 -0400 [thread overview] Message-ID: <d36b1ca3-413a-8a19-ad96-0775593e4337@osg.samsung.com> (raw) In-Reply-To: <5732D0BF.3020207@samsung.com> Hello Krzysztof, On 05/11/2016 02:27 AM, Krzysztof Kozlowski wrote: > On 05/10/2016 11:07 PM, Javier Martinez Canillas wrote: >> Exynos SoCs have a Multi Format Video Hardware Codec (MFC) IP block that >> can be used to {en,de}code video streams by hardware. Enable support for >> its driver as a module so the MFC can be tested. >> >> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> >> >> --- >> >> This patch depends on https://patchwork.kernel.org/patch/8970711/ >> >> arch/arm/configs/multi_v7_defconfig | 1 + >> 1 file changed, 1 insertion(+) > > > Both patches look good but only exynos_defconfig ended in Patchwork. > This one did not... because you forgot to Cc the samsung-soc list. > Sigh, this time I used the cc list suggested by get_maintainers.pl and forgot to double check if was complete. I'll resend and cc samsung-soc. > Best regards, > Krzysztod > Best regards, -- Javier Martinez Canillas Open Source Group Samsung Research America
next prev parent reply other threads:[~2016-05-11 12:15 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-10 21:07 [PATCH 1/2] ARM: exynos_defconfig: Enable MFC driver as module Javier Martinez Canillas 2016-05-10 21:07 ` Javier Martinez Canillas 2016-05-10 21:07 ` [PATCH 2/2] ARM: multi_v7_defconfig: Enable Exynos " Javier Martinez Canillas 2016-05-10 21:07 ` Javier Martinez Canillas 2016-05-11 6:27 ` Krzysztof Kozlowski 2016-05-11 6:27 ` Krzysztof Kozlowski 2016-05-11 12:14 ` Javier Martinez Canillas [this message] 2016-05-11 12:14 ` Javier Martinez Canillas 2016-05-11 12:17 ` Krzysztof Kozlowski 2016-05-11 12:17 ` Krzysztof Kozlowski 2016-05-11 12:18 ` Javier Martinez Canillas 2016-05-11 12:18 ` Javier Martinez Canillas 2016-05-30 6:36 ` [PATCH 1/2] ARM: exynos_defconfig: Enable " Krzysztof Kozlowski 2016-05-30 6:36 ` Krzysztof Kozlowski
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=d36b1ca3-413a-8a19-ad96-0775593e4337@osg.samsung.com \ --to=javier@osg.samsung.com \ --cc=alexandre.belloni@free-electrons.com \ --cc=arnd@arndb.de \ --cc=geert+renesas@glider.be \ --cc=horms+renesas@verge.net.au \ --cc=k.kozlowski@samsung.com \ --cc=kgene@kernel.org \ --cc=lee.jones@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=olof@lixom.net \ --cc=sjoerd.simons@collabora.co.uk \ --cc=treding@nvidia.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.