From: Rahul Sharma <r.sh.open@gmail.com> To: Tomasz Figa <t.figa@samsung.com> Cc: Sachin Kamat <sachin.kamat@linaro.org>, Rahul Sharma <rahul.sharma@samsung.com>, linux-samsung-soc <linux-samsung-soc@vger.kernel.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Kukjin Kim <kgene.kim@samsung.com>, Tomasz Figa <tomasz.figa@gmail.com>, sunil joshi <joshi@samsung.com>, Pankaj Dubey <pankaj.dubey@samsung.com> Subject: Re: [PATCH v7 1/3] ARM: EXYNOS: initial board support for exynos5260 SoC Date: Wed, 9 Apr 2014 14:45:50 +0530 [thread overview] Message-ID: <CAPdUM4OitgCTOT4Eo2Uq-UW95Z1D7yoLrqC_=+==tPAg8kJBtA@mail.gmail.com> (raw) In-Reply-To: <53450D29.7020207@samsung.com> On 9 April 2014 14:34, Tomasz Figa <t.figa@samsung.com> wrote: > On 07.04.2014 10:38, Sachin Kamat wrote: >> >> Hi Rahul, >> >> On 3 April 2014 15:30, Rahul Sharma <rahul.sharma@samsung.com> wrote: >>> >>> From: Pankaj Dubey <pankaj.dubey@samsung.com> >>> >>> This patch add basic arch side support for exynos5260 SoC. >> >> <snip> >> >>> @@ -374,6 +374,7 @@ static char const *exynos_dt_compat[] __initconst = { >>> "samsung,exynos4412", >>> "samsung,exynos5", >>> "samsung,exynos5250", >>> + "samsung,exynos5260", >> >> >> I don't think we should be adding this as we do not yet have any soc >> specific quirk. >> Compatibility to generic string, "samsung,exynos5" should be sufficient. >> > > Yes. Unless a SoC specific quirk that needs to be handled at such low level > stage emerges, there is no need to add such compatible string to the kernel. > Thanks Sachin, Tomasz, I will change this. Regards, Rahul Sharma. > Best regards, > Tomasz
WARNING: multiple messages have this Message-ID (diff)
From: r.sh.open@gmail.com (Rahul Sharma) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v7 1/3] ARM: EXYNOS: initial board support for exynos5260 SoC Date: Wed, 9 Apr 2014 14:45:50 +0530 [thread overview] Message-ID: <CAPdUM4OitgCTOT4Eo2Uq-UW95Z1D7yoLrqC_=+==tPAg8kJBtA@mail.gmail.com> (raw) In-Reply-To: <53450D29.7020207@samsung.com> On 9 April 2014 14:34, Tomasz Figa <t.figa@samsung.com> wrote: > On 07.04.2014 10:38, Sachin Kamat wrote: >> >> Hi Rahul, >> >> On 3 April 2014 15:30, Rahul Sharma <rahul.sharma@samsung.com> wrote: >>> >>> From: Pankaj Dubey <pankaj.dubey@samsung.com> >>> >>> This patch add basic arch side support for exynos5260 SoC. >> >> <snip> >> >>> @@ -374,6 +374,7 @@ static char const *exynos_dt_compat[] __initconst = { >>> "samsung,exynos4412", >>> "samsung,exynos5", >>> "samsung,exynos5250", >>> + "samsung,exynos5260", >> >> >> I don't think we should be adding this as we do not yet have any soc >> specific quirk. >> Compatibility to generic string, "samsung,exynos5" should be sufficient. >> > > Yes. Unless a SoC specific quirk that needs to be handled at such low level > stage emerges, there is no need to add such compatible string to the kernel. > Thanks Sachin, Tomasz, I will change this. Regards, Rahul Sharma. > Best regards, > Tomasz
next prev parent reply other threads:[~2014-04-09 9:15 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-03 10:00 [PATCH v7 0/3] exynos: arch: add support for exynos5260 SoC Rahul Sharma 2014-04-03 10:00 ` Rahul Sharma [not found] ` <1396519224-18712-1-git-send-email-rahul.sharma-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> 2014-04-03 10:00 ` [PATCH v7 1/3] ARM: EXYNOS: initial board " Rahul Sharma 2014-04-03 10:00 ` Rahul Sharma 2014-04-07 8:38 ` Sachin Kamat 2014-04-07 8:38 ` Sachin Kamat 2014-04-09 9:04 ` Tomasz Figa 2014-04-09 9:04 ` Tomasz Figa 2014-04-09 9:15 ` Rahul Sharma [this message] 2014-04-09 9:15 ` Rahul Sharma 2014-04-03 10:00 ` [PATCH v7 2/3] ARM: dts: add dts files " Rahul Sharma 2014-04-03 10:00 ` Rahul Sharma 2014-04-09 10:29 ` Tomasz Figa 2014-04-09 10:29 ` Tomasz Figa 2014-04-03 10:00 ` [PATCH v7 3/3] ARM: dts: add dts files for xyref5260 board Rahul Sharma 2014-04-03 10:00 ` Rahul Sharma 2014-04-07 8:40 ` Sachin Kamat 2014-04-07 8:40 ` Sachin Kamat 2014-04-09 10:52 ` Tomasz Figa 2014-04-09 10:52 ` Tomasz Figa
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='CAPdUM4OitgCTOT4Eo2Uq-UW95Z1D7yoLrqC_=+==tPAg8kJBtA@mail.gmail.com' \ --to=r.sh.open@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=joshi@samsung.com \ --cc=kgene.kim@samsung.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=pankaj.dubey@samsung.com \ --cc=rahul.sharma@samsung.com \ --cc=sachin.kamat@linaro.org \ --cc=t.figa@samsung.com \ --cc=tomasz.figa@gmail.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.