public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox•de>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: Randy Dunlap <rdunlap@infradead•org>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	kbuild test robot <fengguang.wu@intel•com>,
	kbuild@01•org, Dan Carpenter <dan.carpenter@oracle•com>,
	linux-crypto@vger•kernel.org, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH 2/4] DRBG: cleanup of preprocessor macros
Date: Sat, 05 Jul 2014 02:03:42 +0200	[thread overview]
Message-ID: <3976289.yTN4qK0lsl@myon.chronox.de> (raw)
In-Reply-To: <20140704141541.GB27229@gondor.apana.org.au>

Am Freitag, 4. Juli 2014, 22:15:41 schrieb Herbert Xu:

Hi Herbert,

> On Sun, Jun 29, 2014 at 01:37:05PM +0200, Stephan Mueller wrote:
> > When looking into the documentation and trying it I found:
> > 
> > - bool choices allow me to only select one option, and only one
> > 
> > - tristate choices allow me to only select one option, if the initial
> > tristate is set to yes. If the initial tristate is set to module, it
> > allows zero to all options to be set.
> > 
> > That said, neither covers my requirement here: require that at least one
> > option is set, but allow more options.
> 
> I have added the following patch to solve this problem.

Thank you very much for the help. I will test it once it is present on the 
server.
> 
> Please respin your patch against this.

All patches that have been sent so far and not applied will be respun around 
the new code level once the updated code appears on the server.

-- 
Ciao
Stephan

  reply	other threads:[~2014-07-05  0:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28 19:57 [PATCH 0/4] DRBG: Fixes for sparse tool reports Stephan Mueller
2014-06-28 19:58 ` [PATCH 1/4] DRBG: use of kernel linked list Stephan Mueller
2014-07-04 14:11   ` Herbert Xu
2014-06-28 20:00 ` [PATCH 2/4] DRBG: cleanup of preprocessor macros Stephan Mueller
2014-06-29  2:20   ` Stephen Rothwell
2014-06-29  5:07     ` Stephan Mueller
2014-06-29  7:41       ` Randy Dunlap
2014-06-29 11:37         ` Stephan Mueller
2014-07-04 14:15           ` Herbert Xu
2014-07-05  0:03             ` Stephan Mueller [this message]
2014-06-28 20:01 ` [PATCH 3/4] DRBG: Fix format string for debugging statements Stephan Mueller
2014-06-29  2:24   ` Stephen Rothwell
2014-06-29  3:46     ` Stephan Mueller
2014-06-29  3:53       ` Joe Perches
2014-06-29  4:54         ` Stephan Mueller
2014-07-04 11:21         ` Dan Carpenter
2014-07-04 16:57           ` Joe Perches
2014-07-04 23:57             ` Stephan Mueller
2014-07-05  0:09               ` Joe Perches
2014-07-05  0:15                 ` Stephan Mueller
2014-07-05  0:24                   ` Joe Perches
2014-07-05  0:27                     ` Stephan Mueller
2014-06-28 20:04 ` [PATCH 4/4] DRBG: Call CTR DRBG DF function only once Stephan Mueller

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=3976289.yTN4qK0lsl@myon.chronox.de \
    --to=smueller@chronox$(echo .)de \
    --cc=dan.carpenter@oracle$(echo .)com \
    --cc=fengguang.wu@intel$(echo .)com \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=kbuild@01$(echo .)org \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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