From: Logan Gunthorpe <logang@deltatee.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-ntb@googlegroups.com, linux-crypto@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
akpm@linux-foundation.org
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Horia Geantă" <horia.geanta@nxp.com>
Subject: Re: [PATCH v15 0/9] Add io{read|write}64 to io-64-atomic headers
Date: Wed, 4 Apr 2018 09:54:41 -0600 [thread overview]
Message-ID: <515f5c92-ac02-6e09-830e-46ea4d462652@deltatee.com> (raw)
In-Reply-To: <87r2nvmf3b.fsf@concordia.ellerman.id.au>
On 4/4/2018 4:38 AM, Michael Ellerman wrote:
> What's the plan for getting it merged? Seems we don't have one?
Yeah, so far there is no plan. I'm not really sure who's attention I
need to get or how to get it.
> Given it touches two arches and generic stuff and drivers and crypto,
> it's a bit of a mess to merge. It's not really something I want to merge
> via the powerpc tree.
Understood.
> Is there any way to split it? I couldn't immediately see what the hard
> dependencies were between the patches.
Yes, a couple of patches have already been taken by their maintainers
over the last few cycles.
> eg. It looks like I could take the two powerpc patches on their own for
> 4.17, and then the rest could go via other trees?
Yup! If you can take the powerpc patches I can keep trying to get the
rest in. They are largely independent and shouldn't really change
anything without the following patches.
> Is patch 1 stand alone?
Essentially, yes, but patch 5 depends on it seeing it's changing the
same area and is trying to avoid creating the same kbuild warnings that
patch 1 suppresses.
> The other option is to ask Andrew Morton to take it, as he often carries
> these cross-tree type series.
Thanks for the tip! I'll copy him when I repost it after the merge window.
Logan
next prev parent reply other threads:[~2018-04-04 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 23:08 [PATCH v15 0/9] Add io{read|write}64 to io-64-atomic headers Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 1/9] iomap: Use non-raw io functions for io{read|write}XXbe Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 2/9] parisc: iomap: introduce io{read|write}64 Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 3/9] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 4/9] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 5/9] iomap: " Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 6/9] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 7/9] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 8/9] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe
2018-03-27 23:08 ` [PATCH v15 9/9] ntb: ntb_hw_switchtec: Cleanup 64bit IO defines to use the common header Logan Gunthorpe
2018-04-04 10:38 ` [PATCH v15 0/9] Add io{read|write}64 to io-64-atomic headers Michael Ellerman
2018-04-04 15:54 ` Logan Gunthorpe [this message]
2018-04-05 4:48 ` Michael Ellerman
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=515f5c92-ac02-6e09-830e-46ea4d462652@deltatee.com \
--to=logang@deltatee.com \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=horia.geanta@nxp.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=mpe@ellerman.id.au \
/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