From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753917AbaI1MBU (ORCPT ); Sun, 28 Sep 2014 08:01:20 -0400 Received: from mga11.intel.com ([192.55.52.93]:18213 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753840AbaI1MBS (ORCPT ); Sun, 28 Sep 2014 08:01:18 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="392677195" Message-ID: <1411905665.11836.15.camel@karhu> Subject: Re: [PATCH] mtd: ubi: Extend UBI layer debug/messaging capabilities From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Tanya Brokhman Cc: dedeking1@gmail.com, linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org, David Woodhouse , Brian Norris , Richard Weinberger , open list Date: Sun, 28 Sep 2014 15:01:05 +0300 In-Reply-To: <1411886185-7838-1-git-send-email-tlinder@codeaurora.org> References: <1411886185-7838-1-git-send-email-tlinder@codeaurora.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-3.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2014-09-28 at 09:36 +0300, Tanya Brokhman wrote: > If there is more then one UBI device mounted, there is no way to > distinguish between messages from different UBI devices. > Add device number to all ubi layer message types. Hi, the goal looks legit to me, but the patch is so large that I do not think that I can really review it in this form. a) A patch which changes the macros (ubi_err(), etc) b) A set of patches which do not change messages at all, but add the 'ubi' parameter to the places where it is missing. c) A patch which changes the messages. So a) will be the most important patch for the reviewer. b) - more or less mechanical changes of a similar kind. c) - the same. Also, if you add a parameter to 'ubi_err()' and the other printing wrappers, add 'ubi' there, not 'ubi_num'. This will allow to prefix messages with vary different things, not just the device number in the future. So the calls would look like ubi_err(ubi, "inconsistent used_ebs"); Once this is done, the series should be more reviewable. The next thing I'd check is whether we really need to change all the messages, or most of them, or we actually need to change only a small part of them. In the former case, it is OK to do what you do, I guess. In the latter case we probably better off with introducing a separate set of printing macros and leave the existing ones as they are. Thanks! -- Best Regards, Artem Bityutskiy