LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	linux-pci@vger.kernel.org,
	"Linus Walleij" <linus.walleij@linaro.org>,
	llvm@lists.linux.dev, "Minghuan Lian" <minghuan.Lian@nxp.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Bharat Kumar Gogada" <bharat.kumar.gogada@amd.com>,
	"Toan Le" <toan@os.amperecomputing.com>,
	linux-riscv@lists.infradead.org,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"kernel test robot" <lkp@intel.com>,
	"Joyce Ooi" <joyce.ooi@intel.com>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	bcm-kernel-feedback-list@broadcom.com,
	"Mingkai Hu" <mingkai.hu@nxp.com>,
	"Shawn Lin" <shawn.lin@rock-chips.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Ray Jui" <rjui@broadcom.com>,
	linux-tegra@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Roy Zang" <roy.zang@nxp.com>, "Michal Simek" <monstr@monstr.e>
Subject: Re: [PATCH] PCI: Remove unnecessary of_irq.h includes
Date: Thu, 20 Oct 2022 19:17:45 +0200	[thread overview]
Message-ID: <20221020171745.jxne3unbiq5qt2vq@pali> (raw)
In-Reply-To: <20221020134547.GA94120@bhelgaas>

On Thursday 20 October 2022 08:45:47 Bjorn Helgaas wrote:
> [+cc Pali, heads-up for trivial addition of <linux/irqdomain.h> to
> pci-mvebu.c]
...
> pci-mvebu.c also relies on getting <linux/irqdomain.h> via
> <linux/of_irq.h>, but it actually depends on of_irq.h, so I'll just
> add an irqdomain.h include there.
> 
> Bjorn
> 

Ok, that is fine!

  parent reply	other threads:[~2022-10-20 17:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 19:54 [PATCH] PCI: Remove unnecessary of_irq.h includes Bjorn Helgaas
2022-10-19 20:11 ` Conor Dooley
2022-10-19 20:27 ` Roy Zang
2022-10-20  7:08 ` kernel test robot
2022-10-20  7:20   ` Conor Dooley
2022-10-20 13:45     ` Bjorn Helgaas
2022-10-20 13:52       ` Conor Dooley
2022-10-20 17:17       ` Pali Rohár [this message]
2022-10-20  8:09 ` kernel test robot
2022-10-20 13:41   ` Bjorn Helgaas
2022-10-20 15:04     ` Bjorn Helgaas
2022-10-21  0:49     ` [kbuild-all] " Chen, Rong A
2022-10-20 14:13 ` kernel test robot
2022-10-20 15:07   ` Bjorn Helgaas
2022-10-21  0:52     ` [kbuild-all] " Chen, Rong A

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=20221020171745.jxne3unbiq5qt2vq@pali \
    --to=pali@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bharat.kumar.gogada@amd.com \
    --cc=conor.dooley@microchip.com \
    --cc=heiko@sntech.de \
    --cc=helgaas@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=joyce.ooi@intel.com \
    --cc=kishon@kernel.org \
    --cc=kw@linux.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=lpieralisi@kernel.org \
    --cc=minghuan.Lian@nxp.com \
    --cc=mingkai.hu@nxp.com \
    --cc=monstr@monstr.e \
    --cc=rjui@broadcom.com \
    --cc=robh@kernel.org \
    --cc=roy.zang@nxp.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=thierry.reding@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=toan@os.amperecomputing.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