From: Paul Bolle <pebolle@tiscali.nl>
To: maitysanchayan@gmail.com
Cc: arnd@arndb.de, shawn.guo@linaro.org, kernel@pengutronix.de,
stefan@agner.ch, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] soc: Add driver for Freescale Vybrid Platform
Date: Wed, 27 May 2015 18:46:47 +0200 [thread overview]
Message-ID: <1432745207.27695.282.camel@x220> (raw)
In-Reply-To: <20150527130727.GA3374@Sanchayan-Arch.toradex.int>
On Wed, 2015-05-27 at 18:37 +0530, maitysanchayan@gmail.com wrote:
> > > +module_platform_driver(vf610_soc_driver);
> >
> > (The series starting at https://lkml.org/lkml/2015/5/10/131 would allow
> > to use builtin_platform_driver() for built-in only code.)
>
> Thanks for bringing this to my attention. I am subscribed to the mailing
> list however this skipped me.
> However that series has not been merged yet, so I can't use builtin_*
> yet?
Correct.
If that series get merged, which is not certain at all, you might
consider changing this. Probably no one will notice if you don't.
Paul Bolle
next prev parent reply other threads:[~2015-05-27 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 11:36 [PATCH v4 0/2] Implement SoC bus support for Vybrid Sanchayan Maity
2015-05-26 11:36 ` [PATCH v4 1/2] ARM: dts: vfxxx: Add OCOTP and OCROM nodes Sanchayan Maity
2015-05-26 11:36 ` [PATCH v4 2/2] soc: Add driver for Freescale Vybrid Platform Sanchayan Maity
2015-05-27 7:31 ` Paul Bolle
2015-05-27 13:07 ` maitysanchayan
2015-05-27 16:46 ` Paul Bolle [this message]
[not found] ` <20150527130727.GA3374-2b/appYahYAQpivJYWJ5AnfHJb42ZiuNiBNltiLz+yw@public.gmane.org>
2015-05-27 17:28 ` Andreas Färber
[not found] ` <7df753efff77a96da285f0571f1316512787e83c.1432637313.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-27 17:47 ` Joachim Eastwood
2015-05-27 21:42 ` Stefan Agner
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=1432745207.27695.282.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
/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;
as well as URLs for NNTP newsgroup(s).