From: Randy Dunlap <randy.dunlap@oracle.com>
To: Carlos Chinea <carlos.chinea@nokia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC PATCHv2 1/7] HSI: Introducing HSI framework
Date: Fri, 7 May 2010 09:18:08 -0700 [thread overview]
Message-ID: <20100507091808.d294050a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1273248713.7755.7261.camel@localhost>
On Fri, 07 May 2010 19:11:53 +0300 Carlos Chinea wrote:
> Hi,
>
> On Fri, 2010-05-07 at 17:26 +0200, ext Randy Dunlap wrote:
> > On Fri, 7 May 2010 18:18:31 +0300 Carlos Chinea wrote:
> >
> --[snip]--
>
> > > diff --git a/drivers/hsi/Kconfig b/drivers/hsi/Kconfig
> > > new file mode 100644
> > > index 0000000..5af62ce
> > > --- /dev/null
> > > +++ b/drivers/hsi/Kconfig
> > > @@ -0,0 +1,13 @@
> > > +#
> > > +# HSI driver configuration
> > > +#
> > > +menuconfig HSI
> > > + bool "HSI support"
> >
> > Why is this bool instead of tristate?
> > IOW, why can it not be built as a loadable module?
> >
>
> Because, I have not implemented it yet. I was planning to do it later
> on. But of course if it has to be there, I can add the module support
> now.
OK, it can wait, no hurry.
Thanks.
> >
> > > + ---help---
> > > + The "High speed synchronous Serial Interface" is
> > > + synchronous serial interface used mainly to connect
> > > + application engines and cellular modems.
> > > +
> > > +if HSI
> > > +
> > > +endif # HSI
> > > diff --git a/drivers/hsi/Makefile b/drivers/hsi/Makefile
> > > new file mode 100644
> > > index 0000000..b42b6cf
> > > --- /dev/null
> > > +++ b/drivers/hsi/Makefile
> > > @@ -0,0 +1,4 @@
> > > +#
> > > +# Makefile for HSI
> > > +#
> > > +obj-$(CONFIG_HSI) += hsi.o
> >
> >
> > ---
> > ~Randy
> > *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> Br,
> Carlos
>
>
> --
> 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/
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-07 16:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 15:18 [RFC PATCHv2 0/7] HSI framework and drivers Carlos Chinea
2010-05-07 15:18 ` [RFC PATCHv2 1/7] HSI: Introducing HSI framework Carlos Chinea
2010-05-07 15:26 ` Randy Dunlap
2010-05-07 16:11 ` Carlos Chinea
2010-05-07 16:18 ` Randy Dunlap [this message]
2010-05-14 14:22 ` Sebastien Jan
2010-05-18 8:37 ` Carlos Chinea
2010-05-07 15:18 ` [RFC PATCHv2 2/7] OMAP SSI: Introducing OMAP SSI driver Carlos Chinea
2010-05-14 14:41 ` Sebastien Jan
2010-05-18 9:07 ` Carlos Chinea
2010-05-18 14:05 ` Sebastien Jan
2010-05-26 7:27 ` Carlos Chinea
2010-05-07 15:18 ` [RFC PATCHv2 3/7] OMAP SSI: Add OMAP SSI to the kernel configuration Carlos Chinea
2010-05-07 15:18 ` [RFC PATCHv2 4/7] HSI CHAR: Add HSI char device driver Carlos Chinea
2010-05-07 15:18 ` [RFC PATCHv2 5/7] HSI CHAR: Add HSI char device kernel configuration Carlos Chinea
2010-05-07 15:18 ` [RFC PATCHv2 6/7] HSI: Add HSI API documentation Carlos Chinea
2010-05-07 15:18 ` [RFC PATCHv2 7/7] HSI CHAR: Update ioctl-number.txt Carlos Chinea
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=20100507091808.d294050a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=carlos.chinea@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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
Powered by JetHome