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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED 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 33A62ECDE3D for ; Fri, 19 Oct 2018 07:08:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C4F7C21476 for ; Fri, 19 Oct 2018 07:08:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C4F7C21476 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727139AbeJSPMu (ORCPT ); Fri, 19 Oct 2018 11:12:50 -0400 Received: from mail-vs1-f65.google.com ([209.85.217.65]:37483 "EHLO mail-vs1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726340AbeJSPMu (ORCPT ); Fri, 19 Oct 2018 11:12:50 -0400 Received: by mail-vs1-f65.google.com with SMTP id r83so24672063vsc.4; Fri, 19 Oct 2018 00:08:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OLmNJ36LwWMMqsWlkLCeV/YPO9vavlldT3NFPf3a7Oo=; b=mkBkbYQlL9remZ7zIFQc/WRs24XSXsoo+T9zT3xltSGafacSpjD1f0vOAg1sq2gWpJ w6iwa18JMUDv/3it2Ki2oTntrCPf/1l4DfHfy6Jdpt45xKw4RHmHMS8HJ5JH6MPkyvZD qKfRVmjp5S8xYJdCELNLpdx63u7kUqow8sJ8ujG2btWzDp+7EVuMGkWKJPoy1nt8tpOD eO3ebC4rfTmDF5D/b/nMxrnLxouBiiJqq/5NV+ergC4A+LlO2fnAYhOkJfBIhmOqiCL5 1MYJQDM20N2qJ4mjq8fro2iDHpusuietHkXR8MFY5pDVPdrtGJnXO0HSwB8+sAO7r5rH oImw== X-Gm-Message-State: ABuFfohq+rPdNfhU1i9MlAAaEpMsYYuQ1eNi8WouOeSJqDrVfy6uLpIh n1kHca7n6UNkjKwm7OCzEOOFhkNisOvo1XxUl3s= X-Google-Smtp-Source: ACcGV63MZWH9kgfSRarxsGHQippQr9x3U34azOeqL/0fDkSg3YuBDZAUiWZsHYJl0HSyGNXWbm4+scC8JisJDruGpnk= X-Received: by 2002:a67:7b56:: with SMTP id w83mr14117399vsc.152.1539932883023; Fri, 19 Oct 2018 00:08:03 -0700 (PDT) MIME-Version: 1.0 References: <20181017080201.10866-1-hch@lst.de> <20181019070001.GA30556@lst.de> In-Reply-To: <20181019070001.GA30556@lst.de> From: Geert Uytterhoeven Date: Fri, 19 Oct 2018 09:07:51 +0200 Message-ID: Subject: Re: move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2 To: Christoph Hellwig Cc: Masahiro Yamada , Matt Porter , Alex Bounine , Dominik Brodowski , linux-kbuild , linux-pci , scsi , Linux-Arch , Linux Kernel Mailing List , linuxppc-dev Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Christoph, On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig wrote: > On Wed, Oct 17, 2018 at 10:30:49AM +0200, Geert Uytterhoeven wrote: > > Please use "git format-patch -v --cover" to prepare patch series > > for sending with git-send-email. > > > > "-v" to prefix all patches with version number , > > "--cover" to have a "[PATCH 0/]" prefix in the cover letter. > > We had that discussion before and I strongly disagree with messing > up the subject lines like that. The git-send-email defaults are > perfectly fine. Can you please clarify what exactly that would mess up? Documentation/process/submitting-patches.rst even mentions the tags to put in "[PATCH ]"? Without this: - It's hard to visually match your untagged cover letter with the actual patches, - Your individual patches lack the version info, so people cannot see which version review comments in an email reply apply to. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds 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=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=unavailable 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 B8BCAECDE44 for ; Fri, 19 Oct 2018 07:47:33 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 445272083E for ; Fri, 19 Oct 2018 07:47:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 445272083E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 42bygR2jHqzF0gv for ; Fri, 19 Oct 2018 18:47:31 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=209.85.217.68; helo=mail-vs1-f68.google.com; envelope-from=geert.uytterhoeven@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux-m68k.org Received: from mail-vs1-f68.google.com (mail-vs1-f68.google.com [209.85.217.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 42bxnx5GBBzF3ZF for ; Fri, 19 Oct 2018 18:08:05 +1100 (AEDT) Received: by mail-vs1-f68.google.com with SMTP id q15so10401753vso.1 for ; Fri, 19 Oct 2018 00:08:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OLmNJ36LwWMMqsWlkLCeV/YPO9vavlldT3NFPf3a7Oo=; b=COYzGzXNvXggSUb6kHB2YSesJ2LSr61YsLN0rLpQxcOQf49UutC2kCQwywnyCilWK9 1xTWxtZ9o6R4TOPSoDJ10SdGjkXEYiZ4stYn6yO5Pzn7iAnsNsVsYvbRPI77uZFR+9Mm F+jHBgjRcCrWNRai+qCExeGuvRopGW7wNvi6g1nb+srrfa/FYoecUV2Dvc0UlymStbap U5OZm0WyNyJ/uO5qmQHlAosJNIA0IedVRQSEJaAqshAHBKVl34BYyiMzDojXRe0Yq/z8 Z2m2bp/fO0pWpvDjZymUThLEBty/vK++oq+Nsjx+iPOWkLrO+BwgpJbi98aZPyT+0v2a 7S5A== X-Gm-Message-State: ABuFfojkMVotYA31S+k79WFIPdSrnwMMbwyAm3/3sUPEgo1alO/wSl7M QpRmk6fQbsZDX903T00wzj1pNcbiJiXTf/PyiMc= X-Google-Smtp-Source: ACcGV63MZWH9kgfSRarxsGHQippQr9x3U34azOeqL/0fDkSg3YuBDZAUiWZsHYJl0HSyGNXWbm4+scC8JisJDruGpnk= X-Received: by 2002:a67:7b56:: with SMTP id w83mr14117399vsc.152.1539932883023; Fri, 19 Oct 2018 00:08:03 -0700 (PDT) MIME-Version: 1.0 References: <20181017080201.10866-1-hch@lst.de> <20181019070001.GA30556@lst.de> In-Reply-To: <20181019070001.GA30556@lst.de> From: Geert Uytterhoeven Date: Fri, 19 Oct 2018 09:07:51 +0200 Message-ID: Subject: Re: move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2 To: Christoph Hellwig Content-Type: text/plain; charset="UTF-8" X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux-Arch , scsi , linux-kbuild , linux-pci , Linux Kernel Mailing List , Dominik Brodowski , Masahiro Yamada , Alex Bounine , linuxppc-dev Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Hi Christoph, On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig wrote: > On Wed, Oct 17, 2018 at 10:30:49AM +0200, Geert Uytterhoeven wrote: > > Please use "git format-patch -v --cover" to prepare patch series > > for sending with git-send-email. > > > > "-v" to prefix all patches with version number , > > "--cover" to have a "[PATCH 0/]" prefix in the cover letter. > > We had that discussion before and I strongly disagree with messing > up the subject lines like that. The git-send-email defaults are > perfectly fine. Can you please clarify what exactly that would mess up? Documentation/process/submitting-patches.rst even mentions the tags to put in "[PATCH ]"? Without this: - It's hard to visually match your untagged cover letter with the actual patches, - Your individual patches lack the version info, so people cannot see which version review comments in an email reply apply to. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds