Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758272Ab3FUBaw (ORCPT ); Thu, 20 Jun 2013 21:30:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:31006 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758018Ab3FUBav (ORCPT ); Thu, 20 Jun 2013 21:30:51 -0400 Date: Fri, 21 Jun 2013 02:30:45 +0100 From: Alasdair G Kergon To: Geremy Condra Cc: dm-devel@redhat.com, wad@chromium.org, linux-kernel@vger.kernel.org, agk@redhat.com Subject: Re: [dm-devel] [PATCH] dm: verity: Add support for emitting uevents on dm-verity errors. Message-ID: <20130621013045.GJ23042@agk-dp.fab.redhat.com> Mail-Followup-To: Geremy Condra , dm-devel@redhat.com, wad@chromium.org, linux-kernel@vger.kernel.org, agk@redhat.com References: <1371763260-9933-1-git-send-email-gcondra@google.com> <20130621005905.GI23042@agk-dp.fab.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Red Hat UK Ltd. Registered in England and Wales, number 03798903. Registered Office: 64 Baker Street, 4th floor, London, W1U 7DF. User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 792 Lines: 20 On Thu, Jun 20, 2013 at 06:12:07PM -0700, Geremy Condra wrote: > Assuming nobody currently using DM_UEVENT minds it doesn't cause any > problems for me. Any current users object? DM_UEVENT toggles uevents on or off across the whole of device-mapper. If there is no particular need for verity *not* to generate uevents while other parts of device-mapper *are* generating them, then we can make do with just the one Kconfig parameter. (Userspace is still free to ignore particular events.) So let's drop the second config parameter. Alasdair -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/