From: Mark Brown Subject: Re: [PATCH v8 2/2] crypto: driver for Tegra AES hardware Date: Tue, 10 Jan 2012 05:29:00 +0000 Message-ID: <20120110052900.GB5433@sirena.org.uk> References: <1324034755-3295-1-git-send-email-vwadekar@nvidia.com> <1324034755-3295-3-git-send-email-vwadekar@nvidia.com> <4F0A7AA9.6020104@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" To: Varun Wadekar Return-path: Content-Disposition: inline In-Reply-To: <4F0A7AA9.6020104-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-crypto.vger.kernel.org On Mon, Jan 09, 2012 at 10:57:05AM +0530, Varun Wadekar wrote: > Is this patch good to go? I did not receive any comments, so I am > assuming that this patch is good but might have slipped from the > maintainers' list of patches to review. > Can some one please review/ack these changes so that we can move > forward in the review process? You've not CCed the relevant maintainers on the patches so there's a reasonable chance they haven't even seen them, much less reviewed them. You should *always* CC maintainers on patches.