public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: David VomLehn <dvomlehn@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kconfig: Add support for floating point configuration variables
Date: Mon, 13 Apr 2015 08:54:16 +0200	[thread overview]
Message-ID: <1428908056.11113.11.camel@x220> (raw)
In-Reply-To: <552B2D74.7020304@infradead.org>

[Removed Yann, who has disappeared long ago.]

On Sun, 2015-04-12 at 19:44 -0700, Randy Dunlap wrote:
> On 04/12/15 14:16, David VomLehn wrote:
> > Add support for floating point configuration variables using C syntax.
> 
> Missing justification.
> 
> Missing explanation (or deletion) of
> +FILE *log_fp; etc.
> 
> 
> > ---
> >  kconfig-frontends/docs/kconfig-language.txt |    2 +-
> >  kconfig-frontends/frontends/conf/conf.c     |    3 +++
> >  kconfig-frontends/frontends/gconf/gconf.c   |    3 +++
> >  kconfig-frontends/frontends/mconf/mconf.c   |    4 ++++
> >  kconfig-frontends/frontends/nconf/nconf.c   |    3 +++
> >  kconfig-frontends/frontends/qconf/qconf.cc  |    3 +++
> >  kconfig-frontends/libs/parser/symbol.c      |   24 +++++++++++++++++++++---
> >  kconfig-frontends/utils/gettext.c           |    3 +++
> >  8 files changed, 41 insertions(+), 4 deletions(-)

This was apparently not done on top of the kernel's code. Is this
perhaps intended for some out of tree project?

Before you consider to resend this as a patch for the kernel, you should
know that a proper commit explanation is needed, as Randy already told,
before most people even consider actually looking at it. A Signed-off-by
tag will also be required, by the way.

Thanks,


Paul Bolle


      reply	other threads:[~2015-04-13  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 21:16 [PATCH] kconfig: Add support for floating point configuration variables David VomLehn
2015-04-13  2:44 ` Randy Dunlap
2015-04-13  6:54   ` Paul Bolle [this message]

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=1428908056.11113.11.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=dvomlehn@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=rdunlap@infradead.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