linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	dougmill@linux.ibm.com, drt@linux.ibm.com, sukadev@linux.ibm.com,
	tlfalcon@linux.ibm.com, mpe@ellerman.id.au,
	benh@kernel.crashing.org, paulus@samba.org,
	kou.ishizaki@toshiba.co.jp, geoff@infradead.org,
	tanghui20@huawei.com, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: ethernet: Prepare cleanup of powerpc's asm/prom.h
Date: Fri, 06 May 2022 01:20:14 +0000	[thread overview]
Message-ID: <165180001499.16316.17491619640124865110.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <09a13d592d628de95d30943e59b2170af5b48110.1651663857.git.christophe.leroy@csgroup.eu>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  4 May 2022 13:32:17 +0200 you wrote:
> powerpc's asm/prom.h includes some headers that it doesn't
> need itself.
> 
> In order to clean powerpc's asm/prom.h up in a further step,
> first clean all files that include asm/prom.h
> 
> Some files don't need asm/prom.h at all. For those ones,
> just remove inclusion of asm/prom.h
> 
> [...]

Here is the summary with links:
  - [net-next,v3] net: ethernet: Prepare cleanup of powerpc's asm/prom.h
    https://git.kernel.org/netdev/net-next/c/6bff3ffcf6ee

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-05-06  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 11:32 [PATCH net-next v3] net: ethernet: Prepare cleanup of powerpc's asm/prom.h Christophe Leroy
2022-05-06  1:20 ` patchwork-bot+netdevbpf [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=165180001499.16316.17491619640124865110.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=davem@davemloft.net \
    --cc=dougmill@linux.ibm.com \
    --cc=drt@linux.ibm.com \
    --cc=geoff@infradead.org \
    --cc=kou.ishizaki@toshiba.co.jp \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paulus@samba.org \
    --cc=sukadev@linux.ibm.com \
    --cc=tanghui20@huawei.com \
    --cc=tlfalcon@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).