From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <Julia.Lawall@lip6.fr>, kernel-janitors@vger.kernel.org
Cc: linux-nfs@vger.kernel.org,
Stefano Stabellini <sstabellini@kernel.org>,
linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
xen-devel@lists.xenproject.org,
Dan Williams <dan.j.williams@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 00/20] drop useless LIST_HEAD
Date: Sun, 23 Dec 2018 13:13:37 +0100 [thread overview]
Message-ID: <d44a1dfe-691e-cfa2-6c8d-56cca6ae4575@users.sourceforge.net> (raw)
In-Reply-To: <1545555435-24576-1-git-send-email-Julia.Lawall@lip6.fr>
> Drop LIST_HEAD where the variable it declares is never used.
Do you know any more places where calls of other macros can be deleted?
Regards,
Markus
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-23 12:13 UTC|newest]
Thread overview: 17+ 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 02/20] net/mlx5e: " Julia Lawall
2018-12-23 9:40 ` Leon Romanovsky
2018-12-23 8:57 ` [PATCH 16/20] mlxsw: spectrum: " Julia Lawall
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
2019-01-10 11:36 ` Kalle Valo
2018-12-23 12:13 ` SF Markus Elfring [this message]
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
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=d44a1dfe-691e-cfa2-6c8d-56cca6ae4575@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=Julia.Lawall@lip6.fr \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.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=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).