Received: by 10.223.148.5 with SMTP id 5csp7197188wrq; Thu, 18 Jan 2018 02:11:54 -0800 (PST) X-Google-Smtp-Source: ACJfBosh2V9HrUq/gJZHWk8eJzrzaKUTMG4JZ2NdxYcmi9NS81MAXCVZMDEvCMkcZ/ZZvoTk77af X-Received: by 10.99.142.76 with SMTP id k73mr29773133pge.89.1516270314219; Thu, 18 Jan 2018 02:11:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516270314; cv=none; d=google.com; s=arc-20160816; b=oK8o2izK3cQddqo2FY4MCHG1P+3UzuIyd0gINGCFn2mDgf5I1QSWsfApeBOuvFjUP6 4TAK4KyKlueUZOIGx9Zt3puHvABn5MAMV4lg85mWQx6pr5N9NBKtdO5QjkY10lhWrpA5 fzAG9BJCc4amJ/I9CS9rAMDKxLPPs20zXlG0kO7JVrb9QjCt/fRonRjAO74pet1RondE IfJjU20lrogVIH/VDUOLsqU/DKtl/lqO24FLlvpvY+Loe/9eBGGQhAiKLPn3rADflCwJ iMILFOHkOQ77aIBQPKLujmq6Aitgk2JmVt4zB6mVpAiu+ProLDvt0USMq/095g4IQr0t BUFQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:references:in-reply-to:mime-version :dkim-signature:arc-authentication-results; bh=EZ1Dz8eTJS42whUG0YuBMHrTrhnGNywUm/hdkk6E9PE=; b=i9AY3G3ByTf5JfE7H4n8YGtnw6U0b6wqJtEfEK+FK/ueo3XBtQkmfuJ1KDgs5zfsvR GGt65HyotXlcgJ4YR15eC+k6yENzU40d8J6miFZRI3mV90ykOJBqP/iWUO7M9wu9/fJX UTKQlM7vgpaLSH/m6AgWrQYvy+tX686W2UvunbjKKtZMOdkTlqwalMbQUcT5r7nPon7u cXe3uVP8j3I0HaodChNtb5p3aXJoTWPFbNpg6dA0AykdCI+haNh4XgaRUWjpcaHlymZt 3serQu/+IF55qT/ysMUZHU5qhoWmcPJabNQwUPUaHXQYvgtP7RioXv+hkOjAlGhwmfeV eP7g== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=VHcPB5xx; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p2si5689461pgr.379.2018.01.18.02.11.39; Thu, 18 Jan 2018 02:11:54 -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=fail header.i=@gmail.com header.s=20161025 header.b=VHcPB5xx; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755367AbeARJ47 (ORCPT + 99 others); Thu, 18 Jan 2018 04:56:59 -0500 Received: from mail-ot0-f196.google.com ([74.125.82.196]:39898 "EHLO mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754902AbeARJ4z (ORCPT ); Thu, 18 Jan 2018 04:56:55 -0500 Received: by mail-ot0-f196.google.com with SMTP id d9so238471oth.6; Thu, 18 Jan 2018 01:56:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=EZ1Dz8eTJS42whUG0YuBMHrTrhnGNywUm/hdkk6E9PE=; b=VHcPB5xxNY7voOsRL6W+Pw0jYTrrsDkVh4SMNP+vo4H12rq2t+GmP58k+4NQeX2faB HssBNxqQXKRBK/zxZ3NhVGqYmklII8tKU7WzAlgJCOX/m32nnS2u9dPb4PvOtTq4m9Rh XSkWPx0A8HhRjVqoB7LqZHWZRXYsNkBDMiv/4KrknMXLwH8AOoeWJNAyrenDI1CuDJr/ VQ0OukcRbt7C9UD3GprZjiSEsVXOxl+bEQnPM6BUwzlXR6Yo6DgMxv45Vtu3fNAERDdF SdEK6Gckak9yqeIl5Put9Y9yu41NP1OtnxDp+EFtc0Y4BMH7+pctngTDGSXOkNIvQ4UA eGcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=EZ1Dz8eTJS42whUG0YuBMHrTrhnGNywUm/hdkk6E9PE=; b=jWqZ96OVYo9nIRBix25ozwcEbJzbNkzfw5BlmS0qlRC3S5ayoStSmyirmXT+Tgrd4Z AeSamnstSi7DhijIZZg+4O2MnlXKImOlze8KxvVsK9g51CLYOeQnpMb/hjmgIrmt3BTs MfaQSMNNnkA51jCJW2n/TIC+4FXLGB3tRGEpWnt43vmQbWWojYEuCY4dxjyxvDsHA2jj 014+xvjEtuVnEcyEpaBKNnZpAqDffFcPvkmO8hAbbmCjJSm8/ljEQsvZ6llfbHH7bcuh ruBrta0+jJTwQXCYFAI9J9lYVEaP/AXdzS7X+ZpNoj4nIB4pCVePLRYd8HAKKGqe9ElU VJaQ== X-Gm-Message-State: AKwxytcJzReDbjvreQDs3LOUODwFRNsTuzdC5RDcp8GUv+N/vNzjXOeK dH6q1wrk4WFmL9IDu9nfnisAu5ehIN/2hMyMFRo= X-Received: by 10.157.67.90 with SMTP id y26mr2782798oti.229.1516269414306; Thu, 18 Jan 2018 01:56:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.17.89 with HTTP; Thu, 18 Jan 2018 01:56:53 -0800 (PST) In-Reply-To: <790e05e9b9675b3f6ef41693a794d1f09795c151.1515766253.git.green.hu@gmail.com> References: <790e05e9b9675b3f6ef41693a794d1f09795c151.1515766253.git.green.hu@gmail.com> From: Arnd Bergmann Date: Thu, 18 Jan 2018 10:56:53 +0100 X-Google-Sender-Auth: wvNqN70LHMsRUhGZr_Qw7wV3jro Message-ID: Subject: Re: [PATCH v6 03/36] sparc: io: To use the define of ioremap_[nocache|wc|wb] in asm-generic/io.h To: Greentime Hu Cc: Greentime , Linux Kernel Mailing List , linux-arch , Thomas Gleixner , Jason Cooper , Marc Zyngier , Rob Herring , Networking , Vincent Chen , DTML , Al Viro , David Howells , Will Deacon , Daniel Lezcano , linux-serial@vger.kernel.org, Geert Uytterhoeven , Linus Walleij , Mark Rutland , Greg KH , Guo Ren , Randy Dunlap , David Miller , Jonas Bonn , Stefan Kristiansson , Stafford Horne Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: > From: Greentime Hu > > It will be built failed if commit id: d25ea659 is selected. This patch > can fix this build error. > > Signed-off-by: Greentime Hu The change is fine, but the reference to commit 'd25ea659' is not for two reasons: - when you rebase the tree, you will get a different ID - the recommended format for referring to another commit is to list it with 12 digits and the one-line summary like this: commit d25ea659bc37 ("asm-generic/io.h: move ioremap_nocache/ioremap_uc/ioremap_wc/ioremap_=E2=80=A6") - Ideally you use a 'Fixes:' tag in the patch description. You can add these lines in your .gitconfig to help you here [alias] fixes =3D show --format=3D'Fixes: %h (\"%s\")' -s [core] abbrev =3D 12 That will give you a 'git fixes' command to output the Fixes: line in the correct format for future bug fixes. For this particular change, I would actually just merge the two patches into one patch that then doesn't break anything in the first place. Arnd