Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755642Ab3JKNNq (ORCPT ); Fri, 11 Oct 2013 09:13:46 -0400 Received: from mail-ea0-f177.google.com ([209.85.215.177]:46602 "EHLO mail-ea0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751890Ab3JKNNo (ORCPT ); Fri, 11 Oct 2013 09:13:44 -0400 Message-ID: <5257F983.9060904@gmail.com> Date: Fri, 11 Oct 2013 15:13:39 +0200 From: Sylwester Nawrocki User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120412 Thunderbird/11.0.1 MIME-Version: 1.0 To: Tomasz Figa CC: linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, linux-media@vger.kernel.org, alsa-devel@alsa-project.org, Kukjin Kim , Arnd Bergmann , Olof Johansson , Russell King - ARM Linux , Ben Dooks , Linus Walleij , Mauro Carvalho Chehab , Sangbeom Kim , Liam Girdwood , Mark Brown , Jaroslav Kysela , Takashi Iwai , Sylwester Nawrocki , Geert Uytterhoeven , Martin Schwidefsky Subject: Re: [PATCH 3/5] [media] s3c-camif: Use CONFIG_ARCH_S3C64XX to check for S3C64xx support References: <1380392497-27406-1-git-send-email-tomasz.figa@gmail.com> <1380392497-27406-3-git-send-email-tomasz.figa@gmail.com> In-Reply-To: <1380392497-27406-3-git-send-email-tomasz.figa@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 588 Lines: 13 On 09/28/2013 08:21 PM, Tomasz Figa wrote: > Since CONFIG_PLAT_S3C64XX is going to be removed, this patch modifies > the Kconfig entry of s3c-camif driver to use the proper way of checking > for S3C64xx support - CONFIG_ARCH_S3C64XX. > > Signed-off-by: Tomasz Figa Acked-by: Sylwester Nawrocki -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/