public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
	David Miller <davem@davemloft.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	abbotti@mev.co.uk, Ingo Molnar <mingo@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-rdma@vger.kernel.org, yishaih@mellanox.com,
	tariqt@mellanox.com, netdev@vger.kernel.org
Subject: Re: [PATCH 10/12] net/mlx4: replace <linux/radix-tree.h> with <linux/radix-tree-root.h>
Date: Sun, 08 Oct 2017 10:32:22 -0700	[thread overview]
Message-ID: <1507483942.11434.4.camel@perches.com> (raw)
In-Reply-To: <CAK7LNAQ1BeSb14poieRU4uMsnsEHPNL2zSNtWi1TGN=YrK_8jA@mail.gmail.com>

On Mon, 2017-10-09 at 02:29 +0900, Masahiro Yamada wrote:
> The idea is simple; include necessary headers explicitly.

Try that for kernel.h

There's a reason aggregation of #includes is useful.

  reply	other threads:[~2017-10-08 17:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 16:10 [PATCH 00/12] radix-tree: split out struct radix_tree_root out to <linux/radix-tree-root.h> Masahiro Yamada
2017-10-08 16:10 ` [PATCH 01/12] radix-tree: replace <linux/spinlock.h> with <linux/spinlock_types.h> Masahiro Yamada
2017-10-08 16:10 ` [PATCH 02/12] radix-tree: split struct radix_tree_root to <linux/radix-tree-root.h> Masahiro Yamada
2017-10-08 16:10 ` [PATCH 03/12] irqdomain: replace <linux/radix-tree.h> with <linux/radix-tree-root.h> Masahiro Yamada
2017-10-08 16:10 ` [PATCH 04/12] writeback: " Masahiro Yamada
2017-10-08 16:10 ` [PATCH 05/12] iocontext.h: " Masahiro Yamada
2017-10-08 16:10 ` [PATCH 06/12] fs: " Masahiro Yamada
2017-10-08 16:10 ` [PATCH 07/12] blkcg: " Masahiro Yamada
2017-10-08 16:10 ` [PATCH 08/12] fscache: include <linux-radix-tree.h> Masahiro Yamada
2017-10-08 16:10 ` [PATCH 09/12] sh: intc: replace <linux/radix-tree.h> with <linux/radix-tree-root.h> Masahiro Yamada
2017-10-08 16:10 ` [PATCH 10/12] net/mlx4: " Masahiro Yamada
2017-10-08 17:00   ` David Miller
2017-10-08 17:29     ` Masahiro Yamada
2017-10-08 17:32       ` Joe Perches [this message]
2017-10-09  5:55         ` Masahiro Yamada
2017-10-09 12:02         ` Masahiro Yamada
2017-10-08 18:55       ` Leon Romanovsky
2017-10-09  5:56         ` Masahiro Yamada
2017-10-09  6:10           ` Leon Romanovsky
2017-10-08 16:10 ` [PATCH 11/12] net/mlx5: " Masahiro Yamada
2017-10-08 17:00   ` David Miller
2017-10-08 16:10 ` [PATCH 12/12] drm/i915: " Masahiro Yamada
2017-10-08 18:52 ` [PATCH 00/12] radix-tree: split out struct radix_tree_root out to <linux/radix-tree-root.h> Leon Romanovsky
2017-10-09  5:58   ` Masahiro Yamada
2017-10-09  6:05     ` Leon Romanovsky
2017-10-10 12:18 ` Matthew Wilcox
2017-10-10 12:56   ` Masahiro Yamada
2017-10-10 13:20     ` Matthew Wilcox

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=1507483942.11434.4.camel@perches.com \
    --to=joe@perches.com \
    --cc=abbotti@mev.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tariqt@mellanox.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yamada.masahiro@socionext.com \
    --cc=yishaih@mellanox.com \
    /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