linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Tony Ibbs <tibs@tonyibbs.co.uk>
Cc: Linux-embedded <linux-embedded@vger.kernel.org>,
	Tibs at Kynesim <tibs@kynesim.co.uk>,
	Richard Watts <rrw@kynesim.co.uk>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 3/5] Kconfig files and Makefile for KBUS
Date: Sun, 27 Feb 2011 10:19:27 -0800	[thread overview]
Message-ID: <20110227101927.3a15e535.rdunlap@xenotime.net> (raw)
In-Reply-To: <97f70d8d0a9026658bb08d8bb4b054124553a0cb.1298829754.git.tibs@tonyibbs.co.uk>

On Sun, 27 Feb 2011 18:11:46 +0000 Tony Ibbs wrote:

> From: Tibs <tibs@tonyibbs.co.uk>
> 
> Amend the ipc Makefile.
> Add an ipc Kconfig for KBUS.
> Amend the init Kconfig appropriately.
> 
> Signed-off-by: Tony Ibbs <tibs@tonyibbs.co.uk>
> ---
>  init/Kconfig |    3 ++
>  ipc/Kconfig  |   99 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  ipc/Makefile |    5 +++
>  3 files changed, 107 insertions(+), 0 deletions(-)
>  create mode 100644 ipc/Kconfig
> 
> diff --git a/init/Kconfig b/init/Kconfig
> index c972899..a31a6fe 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -339,6 +339,8 @@ config AUDIT_TREE
>  	depends on AUDITSYSCALL
>  	select FSNOTIFY
>  
> +source "ipc/Kconfig"
> +
>  source "kernel/irq/Kconfig"
>  
>  menu "RCU Subsystem"
> @@ -1305,3 +1307,4 @@ config PADATA
>  	bool
>  
>  source "kernel/Kconfig.locks"
> +

You can drop that line.

> diff --git a/ipc/Kconfig b/ipc/Kconfig
> new file mode 100644
> index 0000000..46ebcda
> --- /dev/null
> +++ b/ipc/Kconfig
> @@ -0,0 +1,99 @@
> +config KBUS
> +        tristate "KBUS messaging system"
> +        default m

Use tabs to indent kconfig entry text, like above (not spaces).

Please do not enable new configs unless they are absolutely required.

> +        ---help---
> +	KBUS is a lightweight messaging system, particularly aimed
> +	at embedded platforms. This option provides the kernel support
> +	for mediating messages between client processes.
> +
> +	If you want KBUS support, you should say Y here.
> +
> +	This support can also be built as a module. If so, the module
> +	will be called kbus.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-02-27 18:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27 18:11 [PATCH 0/5] RFC: KBUS messaging subsystem Tony Ibbs
2011-02-27 18:11 ` [PATCH 1/5] Documentation for KBUS Tony Ibbs
2011-02-27 18:11   ` [PATCH 2/5] External header file " Tony Ibbs
2011-02-27 18:11     ` [PATCH 3/5] Kconfig files and Makefile " Tony Ibbs
2011-02-27 18:11       ` [PATCH 4/5] Internal header file " Tony Ibbs
2011-02-27 18:19       ` Randy Dunlap [this message]
2011-02-27 19:36         ` [PATCH 3/5] Kconfig files and Makefile " Tony Ibbs
2011-02-27 19:26 ` [PATCH 5/5] KBUS source file Tony Ibbs
2011-02-27 20:25   ` Randy Dunlap
2011-02-28 19:23   ` Sam Ravnborg
2011-02-28 22:25     ` Tony Ibbs
2011-03-01  5:42       ` Sam Ravnborg
2011-02-28  7:48 ` [PATCH 0/5] RFC: KBUS messaging subsystem Grant Likely
2011-02-28  7:52   ` Grant Likely
2011-02-28 19:13     ` Tony Ibbs

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=20110227101927.3a15e535.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-embedded@vger.kernel.org \
    --cc=rrw@kynesim.co.uk \
    --cc=tibs@kynesim.co.uk \
    --cc=tibs@tonyibbs.co.uk \
    /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).