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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 70A95C5519F for ; Wed, 18 Nov 2020 13:31:36 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 50BB82168B for ; Wed, 18 Nov 2020 13:31:34 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 50BB82168B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=tempfail smtp.mailfrom=dm-devel-bounces@redhat.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-197-UAneWz-EPz6Atcj5731qmQ-1; Wed, 18 Nov 2020 08:31:28 -0500 X-MC-Unique: UAneWz-EPz6Atcj5731qmQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A67256414C; Wed, 18 Nov 2020 13:31:22 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 094B776640; Wed, 18 Nov 2020 13:31:22 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 025928C7B4; Wed, 18 Nov 2020 13:31:18 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 0AIDBkCX000334 for ; Wed, 18 Nov 2020 08:11:46 -0500 Received: by smtp.corp.redhat.com (Postfix) id 257D8B3033; Wed, 18 Nov 2020 13:11:46 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast03.extmail.prod.ext.rdu2.redhat.com [10.11.55.19]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1A21BB3029 for ; Wed, 18 Nov 2020 13:11:41 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id AD05E8007C9 for ; Wed, 18 Nov 2020 13:11:41 +0000 (UTC) Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-449-yYc_PkLuN2qmD1pwOLzo8w-1; Wed, 18 Nov 2020 08:11:39 -0500 X-MC-Unique: yYc_PkLuN2qmD1pwOLzo8w-1 Received: from willy by casper.infradead.org with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfMuz-0006LA-DU; Wed, 18 Nov 2020 12:50:37 +0000 Date: Wed, 18 Nov 2020 12:50:37 +0000 From: Matthew Wilcox To: Jan Beulich Message-ID: <20201118125037.GE29991@casper.infradead.org> References: <20201118084800.2339180-1-hch@lst.de> <22ca5396-0253-f286-9eab-d417b2e0b3ad@suse.com> <20201118085804.GA20384@lst.de> <1ded2079-f1be-6d5d-01df-65754447df78@suse.com> <61044f85-cd41-87b5-3f41-36e3dffb6f2a@suse.com> MIME-Version: 1.0 In-Reply-To: <61044f85-cd41-87b5-3f41-36e3dffb6f2a@suse.com> X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-loop: dm-devel@redhat.com Cc: linux-bcache@vger.kernel.org, Jens Axboe , Mike Snitzer , Konrad Rzeszutek Wilk , Greg KH , Jan Kara , Josef Bacik , Coly Li , linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, dm-devel@redhat.com, linux-mtd@lists.infradead.org, linux-mm@kvack.org, Richard Weinberger , Tejun Heo , xen-devel@lists.xenproject.org, Christoph Hellwig Subject: Re: [dm-devel] merge struct block_device and struct hd_struct X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, Nov 18, 2020 at 10:23:51AM +0100, Jan Beulich wrote: > On 18.11.2020 10:09, Greg KH wrote: > > On Wed, Nov 18, 2020 at 10:04:04AM +0100, Jan Beulich wrote: > >> On 18.11.2020 09:58, Christoph Hellwig wrote: > >>> On Wed, Nov 18, 2020 at 09:56:11AM +0100, Jan Beulich wrote: > >>>> since this isn't the first series from you recently spamming > >>>> xen-devel, may I ask that you don't Cc entire series to lists > >>>> which are involved with perhaps just one out of the many patches? > >>>> IMO Cc lists should be compiled on a per-patch basis; the cover > >>>> letter may of course be sent to the union of all of them. > >>> > >>> No way. Individual CCs are completely broken as they don't provide > >>> the reviewer a context. > >> > >> That's the view of some people, but not all. Context can be easily > >> established by those who care going to one of the many archives on > >> which the entire series lands. Getting spammed, however, can't be > >> avoided by the dozens or hundreds of list subscribers. > > > > kernel patches are never "spam", sorry, but for developers to try to > > determine which lists/maintainers want to see the whole series and which > > do not is impossible. > > > > Patches in a series are easily deleted from sane mail clients with a > > single click/keystroke all at once, they aren't a problem that needs to > > be reduced in volume. > > This doesn't scale, neither in the dimension of recipients nor in > the dimension of possible sources of such series. > > While it may seem small, it's also a waste of resources to have mails > sent to hundreds of even thousands of people. So while from a > technical content perspective I surely agree with you saying 'kernel > patches are never "spam"', they still are from the perspective of > what "spam mail" originally means: Mail the recipients did not want > to receive. What doesn't scale is developers who only care about their tiny sliver of Linux and don't stick their heads up from time to time and look around. This is an opportunity for people to become more involved in the development of Linux as a whole, instead of just worrying about their bit. You're not "a Xen developer". You're a Linux developer whose current focus is on Xen. -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel