[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMhs6Yy_O33jZ5N7E5UuAtjoRyyEcUG8s4-PQwooX-TJ3Wh=2A@mail.gmail.com>
Date: Mon, 15 Aug 2011 02:18:22 +0300
From: Maxin B John <maxin.john@...il.com>
To: rdunlap@...otime.net
Cc: Boaz Harrosh <bharrosh@...asas.com>,
Benny Halevy <bhalevy@...asas.com>,
"James E.J. Bottomley" <JBottomley@...allels.com>,
osd-dev@...n-osd.org, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] SCSI: OSD: Kconfig: Select SHA1 and HMAC for OSD
Initiator library
Ping..
On Thu, Aug 11, 2011 at 5:27 PM, Maxin B. John <maxin.john@...il.com> wrote:
> SCSI_OSD_INITIATOR should select CRYPTO_SHA1 and CRYPTO_HMAC. Express this
> in Kconfig so that the requirements are met automatically.
>
> Signed-off-by: Maxin B. John <maxin.john@...il.com>
> ---
> diff --git a/drivers/scsi/osd/Kconfig b/drivers/scsi/osd/Kconfig
> index 861b5ce..1535fe1 100644
> --- a/drivers/scsi/osd/Kconfig
> +++ b/drivers/scsi/osd/Kconfig
> @@ -11,17 +11,16 @@
> # it under the terms of the GNU General Public version 2 License as
> # published by the Free Software Foundation
> #
> -# FIXME: SCSI_OSD_INITIATOR should select CONFIG (HMAC) SHA1 somehow.
> -# How is it done properly?
> #
>
> config SCSI_OSD_INITIATOR
> tristate "OSD-Initiator library"
> depends on SCSI
> + select CRYPTO
> + select CRYPTO_SHA1
> + select CRYPTO_HMAC
> help
> Enable the OSD-Initiator library (libosd.ko).
> - NOTE: You must also select CRYPTO_SHA1 + CRYPTO_HMAC and their
> - dependencies
>
> config SCSI_OSD_ULD
> tristate "OSD Upper Level driver"
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists