Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp2669394ybv; Mon, 24 Feb 2020 09:20:32 -0800 (PST) X-Google-Smtp-Source: APXvYqzbMD3yRYFjQwx1cQL2XmNjdZEuH00hShyFsFPAxfxHH7l0jkag8+TALNwG13U2B5NhfhC5 X-Received: by 2002:a05:6808:209:: with SMTP id l9mr105501oie.112.1582564832499; Mon, 24 Feb 2020 09:20:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582564832; cv=none; d=google.com; s=arc-20160816; b=BYS+FeuK8vb5rdRX9dFvIa71CIPuvDOR2mXFWH/FSByXjBbhQ/xKOz92vhxq4apIu4 Zq084nIXagBGmxtT6FF3Yt+NDvnpTeU8iEN52VxMiPxcv3E2sB595wj7ncwQ6Zx6L9iX tQbbfWUshbgf8IYQUd2Zj8zyDUfj/CBFJGWhrwFwnjy9vrNds3Ugo2BYDAWSdFC9i6cw rnYyotN9EqS2Dr8gzzqmmHWYXycrUycPVeSxKZXILP/hsYuU/sWhq/4ar+H7qSM0+dus ubeSR0vwLnVL/SGrVTHNG2X62nuwzt/2GSyZ8eFnx+ASoG+Wq49ENBwe1RWe5eE7oLbf qYRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:to :date:from:dkim-signature; bh=gyw3IQoCgUqeHBYgq3kf+BJNZrC8xCDPvwa+Ug1jeIY=; b=t1XmFyWMWY2I++6Yy9fVEGhHisvfhwCEr4CzxvSJRcTb/0FJgCeetZgMWLW2eWGEKl TSHseK1FzVAYY6gR477HJx2M9eNXBA8WtQ0QbxWIh6vLmBQTeV88o/vMJpzAzym1GDcT 6cCKF0UngT37nrOyiS/vK6lmjl7A15CsDEBY1K7LgZECW7JGV3yw+XCjCgz4AvNznjZW 4JH+2pzUaAsfQEWEm+0RK/PlZGxR2knNgOXYTDV0cjlHafMhAudnmZhKGyAYyQcl8HPy LtRo67ZyRtTevMTIUifs3rnLMahhgY4k1t/MyDGQNtfFjR+XtLhl/0PEfFtjgZytKh7V xwgQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@es-iitr-ac-in.20150623.gappssmtp.com header.s=20150623 header.b=rxarjv0j; 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=fail (p=NONE sp=NONE dis=NONE) header.from=iitr.ac.in Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s188si4721316oia.277.2020.02.24.09.20.17; Mon, 24 Feb 2020 09:20:32 -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=@es-iitr-ac-in.20150623.gappssmtp.com header.s=20150623 header.b=rxarjv0j; 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=fail (p=NONE sp=NONE dis=NONE) header.from=iitr.ac.in Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727718AbgBXRSc (ORCPT + 99 others); Mon, 24 Feb 2020 12:18:32 -0500 Received: from mail-pl1-f194.google.com ([209.85.214.194]:41255 "EHLO mail-pl1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727426AbgBXRSc (ORCPT ); Mon, 24 Feb 2020 12:18:32 -0500 Received: by mail-pl1-f194.google.com with SMTP id t14so4311654plr.8 for ; Mon, 24 Feb 2020 09:18:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=es-iitr-ac-in.20150623.gappssmtp.com; s=20150623; h=from:date:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=gyw3IQoCgUqeHBYgq3kf+BJNZrC8xCDPvwa+Ug1jeIY=; b=rxarjv0j6U/0Mn9WePM3dmGAynqBodgb0qcGxwIqrk4TVZWw97sTqpQVtxMP0sFT0S KBZwY3S4PVFCTll37uvZ7vy5EJrgHC/O82hs1PPzVsl2OGg4F2qHiMEMmFBZN5wmBKKL GDCCq7rqcNqv7zWuNGRZvqt/On3TdqBdZDtRNt9jgINp9+YN8wBEI6JYJfj6FUadIC8+ TBEJyhq5fgG2byb3XP37tkPBOHdOEBmZiFy7Jrw298f3NpVkfHbkJ+jWXczGd8vpFwXL 1urlhCWFuMu3jWJEfhVPxC9HDgUCWZjw7BeE6HF61dIhXALyrX0b5+LRyp6KF0FL9V02 7qsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=gyw3IQoCgUqeHBYgq3kf+BJNZrC8xCDPvwa+Ug1jeIY=; b=fs8amMXI1nT/t0G/jqLNFoQlf8KizkYjmfBD3VkDsCNtX6srRpbGqUD7X9YoB6U/n2 dXRnksvL9hJKw1PYqcgWZnVdEq86NEK/wUPmOcArKTyZ8iJqwOnwKT870lwsWaXqrf96 T5pYYYwhNQvKet8rRBU0UE0rx4qs2Vq7pTUXMe4kxztNrb2n1GDOZ6BvQHEPuutGnIRF 1JdUimjJE1By1oEE8fPhPJ+bXMR0zeYLgHwzlhO0bwMuQQ9ex+39cRhPJF89ojE3kxiT RVqf+ZievgkbNeKVCx2qZpb8zRRKfOjPqF2qnG6akuTFhSMGYTHIm5TOVb3krquk3biz TIZg== X-Gm-Message-State: APjAAAXoO6MvDyFZfTpS7LhXPH+HVSCrPda2RO8zREgUR6AkNdyDm830 BQOCviOWnqIpqqLpaoi1P4kvT6nVCRQdnjRQ X-Received: by 2002:a17:90a:c691:: with SMTP id n17mr80171pjt.41.1582564711576; Mon, 24 Feb 2020 09:18:31 -0800 (PST) Received: from kaaira-HP-Pavilion-Notebook ([103.37.201.170]) by smtp.gmail.com with ESMTPSA id t8sm29369pjy.20.2020.02.24.09.18.28 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 24 Feb 2020 09:18:30 -0800 (PST) From: Kaaira Gupta X-Google-Original-From: Kaaira Gupta Date: Mon, 24 Feb 2020 22:48:23 +0530 To: Joe Perches , Manish Chopra , GR-Linux-NIC-Dev@marvell.com, Greg Kroah-Hartman , netdev@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4] staging: qlge: emit debug and dump at same level Message-ID: <20200224171823.GA8240@kaaira-HP-Pavilion-Notebook> References: <20200224082448.GA6826@kaaira-HP-Pavilion-Notebook> <84410699e6acbffca960aa2944e9f5869478b178.camel@perches.com> <20200224164721.GA7214@kaaira-HP-Pavilion-Notebook> <9f0d39d5972553b86123873294fc9f9566130036.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9f0d39d5972553b86123873294fc9f9566130036.camel@perches.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 24, 2020 at 08:54:43AM -0800, Joe Perches wrote: > On Mon, 2020-02-24 at 22:17 +0530, Kaaira Gupta wrote: > > On Mon, Feb 24, 2020 at 05:38:09AM -0800, Joe Perches wrote: > > > On Mon, 2020-02-24 at 13:54 +0530, Kaaira Gupta wrote: > > > > Simplify code in ql_mpi_core_to_log() by calling print_hex_dump() > > > > instead of existing functions so that the debug and dump are > > > > emitted at the same KERN_ > > > [] > > > > diff --git a/drivers/staging/qlge/qlge_dbg.c b/drivers/staging/qlge/qlge_dbg.c > > > [] > > > > @@ -1324,27 +1324,10 @@ void ql_mpi_core_to_log(struct work_struct *work) > > > > { > > > > struct ql_adapter *qdev = > > > > container_of(work, struct ql_adapter, mpi_core_to_log.work); > > > > - u32 *tmp, count; > > > > - int i; > > > > > > > > - count = sizeof(struct ql_mpi_coredump) / sizeof(u32); > > > > - tmp = (u32 *)qdev->mpi_coredump; > > > > - netif_printk(qdev, drv, KERN_DEBUG, qdev->ndev, > > > > - "Core is dumping to log file!\n"); > > > > > > There is no real need to delete this line. > > > > > > And if you really want to, it'd be better to mention > > > the removal in the commit message description. > > > > > > As is for this change, there is no "debug" and "dump" > > > as the commit message description shows, just "dump". > > > > This patch has already been added to the tree, > > What tree is that? > It's not in -next as of right now. Its in staging-next right now. This is the link: https://lore.kernel.org/driverdev-devel/cba75ee4d88afdf118631510ad0f971e42c1a31c.camel@perches.com/ > > > if I amend the commit now > > using git rebase, won't it affect the upstream as the SHA-1 of the > > commit and it's children will change? > > You are sending patches not pull requests. > > If it's really in an actual tree that people > care about, send another patch putting the > netif_printk back. I'll submit a patch, but can you please explain me why this function is still needed when we are already using print_hex_dump()? > >