From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755964AbbHGCDX (ORCPT ); Thu, 6 Aug 2015 22:03:23 -0400 Received: from mail-pa0-f53.google.com ([209.85.220.53]:33571 "EHLO mail-pa0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755213AbbHGCDV (ORCPT ); Thu, 6 Aug 2015 22:03:21 -0400 Date: Fri, 7 Aug 2015 11:03:56 +0900 From: Sergey Senozhatsky To: Joe Perches , minchan@kernel.org Cc: Sergey Senozhatsky , Salah Triki , ngupta@vflare.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] zram: Replace pr_* with dev_* Message-ID: <20150807020356.GC1891@swordfish> References: <20150807000520.GA1891@swordfish> <1438910251.2322.2.camel@perches.com> <20150807014212.GB1891@swordfish> <1438912113.2322.7.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1438912113.2322.7.camel@perches.com> User-Agent: Mutt/1.5.23+102 (2ca89bed6448) (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (08/06/15 18:48), Joe Perches wrote: [..] > > And I saw some time ago people doing that type of thing. So I'd like > > to avoid unnecessary pain for zram users even if the messages are not > > guaranteed to remain stable between kernel releases. Just my opinion. [..] > because dmesg is not an ABI. I absolutely agree, this is debatable and controversial. I saw people grepping dmesg and they treated error messages just like errno codes or like additional info to attach to errno. Whether we like or not, but, it seems, for that cases error message is more or less part of ABI. It's fine when we change _info message, but touching _warn or _err message is a bit different thing, *I think*. Let's hear from Minchan. -ss