linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Tom Psyborg <pozega.tomislav@gmail.com>,
	Julia Lawall <julia.lawall@lip6.fr>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	kernel-janitors@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Dan Williams <dan.j.williams@intel.com>,
	linux-scsi@vger.kernel.org, linux-nfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-btrfs@vger.kernel.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/20] drop useless LIST_HEAD
Date: Sat, 29 Dec 2018 07:19:35 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1812290717010.2673@hadrien> (raw)
In-Reply-To: <20181229052504.GA16315@magnolia>



On Fri, 28 Dec 2018, Darrick J. Wong wrote:

> On Thu, Dec 27, 2018 at 04:40:55PM +0300, Dan Carpenter wrote:
> > On Tue, Dec 25, 2018 at 11:12:20PM +0100, Tom Psyborg wrote:
> > > there was discussion about this just some days ago. CC 4-5 lists is
> > > more than enough
> > >
> >
> > I don't know who you were discussing this with...
> >
> > You should CC the 0th patch to all the mailinglists.  That much is a
> > clear rule.
> >
> > For the rest, Julia's position is the more conservative one.  I was in
> > a conversation in RL and they were like, "CC everyone for all the
> > patches".  It depends on the context, of course.  If the patches are
> > dependent on each other then you *have* to CC everyone for everything.
>
> Agreed.  Ms. Lawall, sending "Cover letter + all relevant XFS patches"
> (as you did) was exactly the right thing for us xfs types. :)
>
> For that matter, we prefer to receive through linux-xfs more patches
> than necessary (one can send the entire series if one is unsure) than to
> go wanting for more context.

Thanks for the confirmation.  I was planning to ignore the 4-5 advice,
because there is no way in this case to make a meaningful 4-5 list
suggestion - it's either all or nothing.  But 20 patches at once is
perhaps a lot as well.  In this case, I just wanted to get rid of the
whole issue at once.

julia

      reply	other threads:[~2018-12-29  6:19 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-23  8:56 [PATCH 00/20] drop useless LIST_HEAD Julia Lawall
2018-12-23  8:56 ` [PATCH 01/20] nfsd: " Julia Lawall
2018-12-23 21:26   ` J. Bruce Fields
2018-12-23  8:56 ` [PATCH 02/20] net/mlx5e: " Julia Lawall
2018-12-23  9:40   ` Leon Romanovsky
2018-12-23  8:56 ` [PATCH 03/20] scsi: lpfc: lpfc_nvme: " Julia Lawall
2018-12-23  8:56 ` [PATCH 04/20] scsi: lpfc: lpfc_scsi: " Julia Lawall
2018-12-23  8:57 ` [PATCH 05/20] scsi: lpfc: lpfc_sli: " Julia Lawall
2018-12-23  8:57 ` [PATCH 06/20] IB/ipoib: " Julia Lawall
2018-12-23  9:41   ` Leon Romanovsky
2019-01-02 22:48   ` Jason Gunthorpe
2018-12-23  8:57 ` [PATCH 07/20] dmaengine: at_hdmac: " Julia Lawall
2018-12-24  9:36   ` Ludovic Desroches
2019-01-02  6:04   ` Vinod Koul
2018-12-23  8:57 ` [PATCH 08/20] xfs: xfs_buf: " Julia Lawall
2018-12-23 22:51   ` Darrick J. Wong
2018-12-24  6:32     ` Julia Lawall
2018-12-23  8:57 ` [PATCH 09/20] xfs: xfs_fsops: " Julia Lawall
2018-12-23 22:51   ` Darrick J. Wong
2018-12-23  8:57 ` [PATCH 10/20] scsi: qla2xxx: " Julia Lawall
2018-12-23  8:57 ` [PATCH 11/20] Btrfs: " Julia Lawall
2019-01-02 16:40   ` David Sterba
2018-12-23  8:57 ` [PATCH 12/20] dmaengine: dw: " Julia Lawall
2019-01-02  6:03   ` Vinod Koul
2018-12-23  8:57 ` [PATCH 13/20] xenbus: " Julia Lawall
2019-01-08  6:58   ` Juergen Gross
2018-12-23  8:57 ` [PATCH 14/20] dmaengine: st_fdma: " Julia Lawall
2019-01-02  6:03   ` Vinod Koul
2018-12-23  8:57 ` [PATCH 15/20] NFS: " Julia Lawall
2019-02-21 22:40   ` Trond Myklebust
2018-12-23  8:57 ` [PATCH 16/20] mlxsw: spectrum: " Julia Lawall
2018-12-23  8:57 ` [PATCH 17/20] dmaengine: pl330: " Julia Lawall
2019-01-02  6:04   ` Vinod Koul
2018-12-23  8:57 ` [PATCH 18/20] dmaengine: sa11x0: " Julia Lawall
2019-01-02  6:04   ` Vinod Koul
2018-12-23  8:57 ` [PATCH 19/20] net/mlx4_core: " Julia Lawall
2018-12-23  8:57 ` [PATCH 20/20] cw1200: " Julia Lawall
2019-01-08 16:30   ` Kalle Valo
2019-01-08 16:44     ` Julia Lawall
2019-01-10 11:36   ` Kalle Valo
2018-12-23 21:49 ` [PATCH 00/20] " Tom Psyborg
2018-12-23 22:06   ` Julia Lawall
2018-12-25 22:12     ` Tom Psyborg
2018-12-27 13:40       ` Dan Carpenter
2018-12-29  5:25         ` Darrick J. Wong
2018-12-29  6:19           ` Julia Lawall [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1812290717010.2673@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dan.j.williams@intel.com \
    --cc=darrick.wong@oracle.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pozega.tomislav@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).