From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2EE6DC2B9F4 for ; Thu, 17 Jun 2021 08:38:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F2E8A613F8 for ; Thu, 17 Jun 2021 08:38:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230494AbhFQIkV (ORCPT ); Thu, 17 Jun 2021 04:40:21 -0400 Received: from mga11.intel.com ([192.55.52.93]:27829 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229712AbhFQIkU (ORCPT ); Thu, 17 Jun 2021 04:40:20 -0400 IronPort-SDR: N+EsSaTQKye2857rYYdNSwNpWUY7nPZy6oLyOcZTf/uTupgE0yGGmD6ELEed5FIKVKRe9E59ns YaA6MTjCut5Q== X-IronPort-AV: E=McAfee;i="6200,9189,10017"; a="203304379" X-IronPort-AV: E=Sophos;i="5.83,280,1616482800"; d="scan'208";a="203304379" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jun 2021 01:38:07 -0700 IronPort-SDR: 9r7wPOkRinaRCAffzfvHg029xMVOmn1+JTqDN6uVhCZAIMRnE6e9HWCmzqZe3c1GWpvAZ2Xs4E 5vTyScrMPg/g== X-IronPort-AV: E=Sophos;i="5.83,280,1616482800"; d="scan'208";a="621983357" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jun 2021 01:38:04 -0700 Received: from andy by smile with local (Exim 4.94) (envelope-from ) id 1ltnXE-0033F6-Bv; Thu, 17 Jun 2021 11:38:00 +0300 Date: Thu, 17 Jun 2021 11:38:00 +0300 From: Andy Shevchenko To: kernel test robot Cc: Chris Down , linux-kernel@vger.kernel.org, kbuild-all@lists.01.org, Petr Mladek , Jessica Yu , Sergey Senozhatsky , John Ogness , Steven Rostedt , Greg Kroah-Hartman , Johannes Weiner , Kees Cook Subject: Re: [PATCH v7 4/5] printk: Userspace format indexing support Message-ID: References: <202106171546.7koPrJBA-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202106171546.7koPrJBA-lkp@intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 17, 2021 at 03:36:08PM +0800, kernel test robot wrote: > Hi Chris, > > I love your patch! Perhaps something to improve: > > [auto build test WARNING on jeyu/modules-next] > [also build test WARNING on linux/master soc/for-next openrisc/for-next powerpc/next asm-generic/master driver-core/driver-core-testing linus/master v5.13-rc6 next-20210616] > [cannot apply to uml/linux-next tip/x86/core] > [If your patch is applied to the wrong git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch] > > url: https://github.com/0day-ci/linux/commits/Chris-Down/printk-Userspace-format-indexing-support/20210617-101450 > base: https://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git modules-next Not sure that has what Andrew keeps in his quilt. Chris, to avoid such issues, use `git format-patch --base ...` when sending a series / patches. -- With Best Regards, Andy Shevchenko