From: Jakub Kicinski <kuba@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] sungem: Prepare cleanup of powerpc's asm/prom.h
Date: Wed, 6 Apr 2022 09:39:18 -0700 [thread overview]
Message-ID: <20220406093918.35b97b2e@kernel.org> (raw)
In-Reply-To: <f43aa220-dcef-bc4b-ebb5-74268581e3e6@csgroup.eu>
On Wed, 6 Apr 2022 05:53:46 +0000 Christophe Leroy wrote:
> Le 05/04/2022 à 22:22, Jakub Kicinski a écrit :
> > On Sat, 2 Apr 2022 12:17:13 +0200 Christophe Leroy wrote:
> >> powerpc's asm/prom.h brings some headers that it doesn't
> >> need itself.
> >>
> >> In order to clean it up, first add missing headers in
> >> users of asm/prom.h
> >
> > Could you resend the net-next patches you had?
>
> Sure I can but,
>
> >
> > They got dropped from patchwork due to net-next being closed during
> > the merge window.
>
> https://patchwork.kernel.org/project/netdevbpf/list/?series=&submitter=192363&state=*&q=&archive=&delegate=
>
> As far as I can see they are in patchwork and two of them have been
> accepted, and this one is tagged as 'deferred', so do I have to resend it ?
Erm, perhaps a clerical error? I don't see them in the tree.
I'd resend both.
next prev parent reply other threads:[~2022-04-06 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 10:17 [PATCH net-next] sungem: Prepare cleanup of powerpc's asm/prom.h Christophe Leroy
2022-04-05 20:22 ` Jakub Kicinski
2022-04-06 5:53 ` Christophe Leroy
2022-04-06 16:39 ` Jakub Kicinski [this message]
2022-04-15 8:45 ` Christophe Leroy
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=20220406093918.35b97b2e@kernel.org \
--to=kuba@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).