Received: by 10.223.164.202 with SMTP id h10csp46007wrb; Tue, 7 Nov 2017 02:37:49 -0800 (PST) X-Google-Smtp-Source: ABhQp+S5dF2e3WncHmdpd3/RkrZPjXEVBF3ggn0o0lIqxdfGMl7zfTQ5fkeAfiwxohOlxHx2NYzC X-Received: by 10.99.95.137 with SMTP id t131mr18238408pgb.330.1510051069635; Tue, 07 Nov 2017 02:37:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510051069; cv=none; d=google.com; s=arc-20160816; b=RgwW3+qCVdJQccCEsKwRmfwyGqrxP+NSoyDx4KvwoWwGRtV+waSKJDgGs/08Fc9dZP DQuVngRRG6DPPit/t+0la3HnVU4q1iZEB7pXJ3I25LyQSOw4bc2hx/ljkAj/9TzrWl71 /Uq1QFtUTgCY712lFr6Pdcs6HzpIZzAkeqTOhe0WuroGwdiByWgQWbwspwvk8ZSW9iSU L47DePOpR4lcM9CCVatwvpTqa2K8VzkhQdC1B64KDhFR5q3tB1iks+AqHsUvPkmQ9mAe STrXQ00h3KTOWVMfpyFFWzVwHL2jIm6+BgB2u9YIskBZzT9pHylvQLsLtlVXXve+3Y5C trag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=GnwWB1UhEOjsfjX4SZgsbk3vLAJiXd/t7CRtWglvAo0=; b=zYqsyKIubiMG0qR9WUHABnWS0/1MjB18wEmRttCysVNqNXLF27KIxqTO+KZnnqrI2p WO9ck7qzeg97puYUNQqcPdyMiDsmjGtEHhJP8QJkxqxc6FxCJTY911azpCJx74hBs5j+ bncQ91HpiXJdhv0usuuIhxBtA3YT/QoYfJITDFVAdYRDS/oFnbystBBpEYv1IJb69WLN 0RHzTx5sj+qGqsFcjYydYvsEyPkTx5P4ga1NA38TwxVacTGG+d+7JlNNtEIKWsDVZiHO RGTbK5ek+pXgOTi7l5nPRee76wbHxgEjd6N5JFoRH7lfTce3yNFEkUMQ1vSan5ksEYVU YYFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=HMVECz6W; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k8si850215pgn.524.2017.11.07.02.37.36; Tue, 07 Nov 2017 02:37:49 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=HMVECz6W; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933184AbdKGDUt (ORCPT + 91 others); Mon, 6 Nov 2017 22:20:49 -0500 Received: from mail-it0-f68.google.com ([209.85.214.68]:46031 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754297AbdKGDUq (ORCPT ); Mon, 6 Nov 2017 22:20:46 -0500 Received: by mail-it0-f68.google.com with SMTP id n195so750626itg.0; Mon, 06 Nov 2017 19:20:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GnwWB1UhEOjsfjX4SZgsbk3vLAJiXd/t7CRtWglvAo0=; b=HMVECz6WBafCaNB5YUtlGhqvy3U66qZw5kiEdqMQHePL4wrmNlIPRKL8wZpUAyK1aS w7olMBebuqS2au39beDi/H0gI+98rW79JtxOiWmxhXQjpKx0ZJRYLVGvtBiocZU0lVrG sG+hm0dEf345DVKWwX8EQF+qna+uDi4qdaez7nSr7iu+pt/WDUgExcqw7Xb0pV0INgTH doehX7EBstDZ5y8HLvMy8LsF1dYvbMHt5SOVP6hk6IqEXtVmkSmtFtuqpKQ198+5nl/O GbWbxnzfhb8MTX65sSdxUA5x/0hK/D8XN/y7LAzEMz8KmQGdRZ/pAQPiOYMsF0SevoI7 4Sjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GnwWB1UhEOjsfjX4SZgsbk3vLAJiXd/t7CRtWglvAo0=; b=pTthlvVxxY4w71HTejXS+300QcKwGXsqSF2weRTqiCXGJ3VtrMDGuDFeVemIeQONc5 anOwCNyFpqLtB7T8T0AyNyKr9qtsve45RWOpSDv1iGqqlSiHwcRu8//XoZKfiA1an335 nvf6MJGkO5Ik3PsHkSFeG78ZhqlI5lbwFqNG77IC188TGGq0Bawk/sj0w/RCLNCqR6bB RabyLQ6JoR74wk6Nm3qWLvxqDa/zqIRkrNLEAdmAxm3SCIsuhldklrsTSlTh4YqiSjxG Hpa7WIYgv7BAJRPbdL9/CEONAIc79vxvkNmqlKJMrAdGXYuCyFrx5lfoIpcSjla3wIEv 54wA== X-Gm-Message-State: AJaThX5o85Ml/BSQNUQLihb+F288FM61bRpxIOKVKpsnvmze93x6deE3 kQqituFY9zbePpotyrRzOmkrueSrRYh6l7qGQCk= X-Received: by 10.36.31.8 with SMTP id d8mr477798itd.80.1510024845363; Mon, 06 Nov 2017 19:20:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.182.140 with HTTP; Mon, 6 Nov 2017 19:20:44 -0800 (PST) In-Reply-To: <20171106022704.GD26011@ziepe.ca> References: <20171031200503.GC18578@ziepe.ca> <20171105110506.usxmuzrvcjvxahr6@linux.intel.com> <20171106022704.GD26011@ziepe.ca> From: PrasannaKumar Muralidharan Date: Tue, 7 Nov 2017 08:50:44 +0530 Message-ID: Subject: Re: [PATCH v2] tpm: Move Linux RNG connection to hwrng To: Jason Gunthorpe Cc: Jarkko Sakkinen , Stefan Berger , linux-integrity@vger.kernel.org, David Howells , Herbert Xu , Dmitry Kasatkin , open list , "open list:INTEGRITY MEASUREMENT ARCHITECTURE (IMA)" , "open list:KEYS-TRUSTED" , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , James Morris , Matt Mackall , David Safford , Mimi Zohar , "Serge E. Hallyn" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jason, On 6 November 2017 at 07:57, Jason Gunthorpe wrote: > On Sun, Nov 05, 2017 at 01:05:06PM +0200, Jarkko Sakkinen wrote: > >> I asked to create a series for a reason. Now this doesn't apply because I >> don't have an ancestor in my git history. > > It would be unusual for me to put your patch into a series unless I am > also adopting it. eg what happens if there are more comments on it? > > Also, I wasn't sure what branch your patch was against since my tree > didn't have history for it either.. > > Sometimes the maintainer has to sort stuff like this out... :) > >> Please resend as series together with my patch. I can apply neither yet >> because they have zero tested-by's. > > Hopefully PrasannaKumar can test both patches. I am assuming you are talking about the following patches - using struct tpm_chip instead of chip number and this patch. I won't be able to test if struct tpm_chip usage as I don't have multiple tpm hw in one machine. In case of tpm rng changes I can test only the lifecycle of tpm rng device. Is that enough? I feel my test will be limited. Please provide your thoughts on this. Regards, PrasannaKumar From 1583281913898978111@xxx Mon Nov 06 02:28:16 +0000 2017 X-GM-THRID: 1582805030856907824 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread