public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Martin Walch <walch.martin@web.de>
Cc: linux-kbuild@vger.kernel.org, "Michal Marek" <mmarek@suse.cz>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Jiri Kosina" <trivial@kernel.org>,
	"Benjamin Poirier" <bpoirier@suse.de>,
	"Dirk Gouders" <dirk@gouders.net>,
	"Wang YanQing" <udknight@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jean Delvare" <jdelvare@suse.de>,
	"Kees Cook" <keescook@chromium.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] kconfig: cleanups, documentation updates, and one bug fix
Date: Tue, 8 Oct 2013 23:32:11 +0200	[thread overview]
Message-ID: <20131008213211.GB3373@free.fr> (raw)
In-Reply-To: <3926659.JuuXvBGSjN@tacticalops>

Martin, All,

On 2013-10-03 19:24 +0200, Martin Walch spake thusly:
> In this second attempt, I tried to incorporate all replies I received for the
> first version of this patch set:

Since there have been positive reviews for thie patches in this series,
I'll take it in my tree.

Regards,
Yann E. MORIN.

> PATCH 1: kconfig: add short explanation to SYMBOL_WRITE
>  Ignore this one as long as there is no clear conclusion about the purpose
>  of SYMBOL_WRITE. I only include it, so the patch numbers do not change and
>  there is no "hole" in the patch set.
> 
> PATCH 2: kconfig: fix trivial typos and update mconf documentation
>  In the first place, this corrected only three typos. Now this patch corrects
>  all bad occurrences of "tell" instead of "tells" and fixes several more
>  spelling mistakes. Furthermore some changes that have been made to mconf
>  during the last years are now also updated in the documentation.
> 
> PATCH 3: kconfig: adjust warning message for conflicting types
>  Now explicitely state that the second type is being ignored.
> 
> PATCH 4: kconfig: remove unused definition from scanner
>  No changes since the first version.
> 
> PATCH 5: kconfig: fix bug in search results string: use strlen(gstr->s), not gstr->len
>  As I do not think it is worth to make this a separate patch, I appended
>  this fix for a bug that is only triggered by the search function of mconf.
> 
> Martin Walch (5):
>   kconfig: add short explanation to SYMBOL_WRITE
>   kconfig: fix trivial typos and update mconf documentation
>   kconfig: adjust warning message for conflicting types
>   kconfig: remove unused definition from scanner
>   kconfig: fix bug in search results string: use strlen(gstr->s), not
>     gstr->len
> 
>  scripts/kconfig/expr.h   |  2 +-
>  scripts/kconfig/mconf.c  | 60 +++++++++++++++++++++++-------------------------
>  scripts/kconfig/menu.c   | 11 +++++----
>  scripts/kconfig/symbol.c |  2 +-
>  scripts/kconfig/zconf.l  |  1 -
>  5 files changed, 37 insertions(+), 39 deletions(-)
> 
> -- 
> 1.8.1.5
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2013-10-08 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 17:24 [PATCH v2 0/5] kconfig: cleanups, documentation updates, and one bug fix Martin Walch
2013-10-08 21:32 ` Yann E. MORIN [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=20131008213211.GB3373@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=akpm@linux-foundation.org \
    --cc=arve@android.com \
    --cc=bpoirier@suse.de \
    --cc=dirk@gouders.net \
    --cc=jdelvare@suse.de \
    --cc=keescook@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=trivial@kernel.org \
    --cc=udknight@gmail.com \
    --cc=walch.martin@web.de \
    /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