All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 23
Date: Tue, 24 Jul 2018 00:35:22 +1000	[thread overview]
Message-ID: <877elmhvf9.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180723200032.221a8f18@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> Changes since 20180720:
>
> Dropped trees: xarray, ida (complex conflicts)
>
> The drm-msm tree gained a conflict against the drm tree and a build
> failure due to an interaction with the drm tree for which I added a
> merge fix patch.
>
> The kvm-arm tree gained a conflict against the arm64 tree.
>
> The driver-core tree gained a conflict against the net-next tree.
>
> The xarray tree gained complex conflicts against the nvdimm tree so I have
> dropped it for today (along with the ida tree that is built on top of it).
>
> The akpm-current tree gained a conflict against Linus' tree and also a
> build failure for which I reverted a commit.
>
> Non-merge commits (relative to Linus' tree): 7606
>  7110 files changed, 316203 insertions(+), 143278 deletions(-)

Hi Stephen,

Would you mind adding my "topic/hvc" branch to linux-next.

We (ppc) are notionally the maintainers for that code but it's used by
some other folks, so I'd like it to get some wider testing before I
commit it.

You should get:

  9f65b81f36e3 ("tty: hvc: introduce the hv_ops.flush operation for hvc drivers")

cheers

  reply	other threads:[~2018-07-23 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 10:00 linux-next: Tree for Jul 23 Stephen Rothwell
2018-07-23 14:35 ` Michael Ellerman [this message]
2018-07-23 21:03   ` Stephen Rothwell
2018-07-23 17:31 ` linux-next: Tree for Jul 23 (netfilter) Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2025-07-23  2:45 linux-next: Tree for Jul 23 Stephen Rothwell
2024-07-23  3:57 Stephen Rothwell
2021-07-23  8:08 Stephen Rothwell
2021-07-25 23:26 ` Mark Brown
2020-07-23 10:11 Stephen Rothwell
2019-07-23  4:23 Stephen Rothwell
2015-07-23  6:57 Stephen Rothwell
2014-07-23  8:51 Stephen Rothwell
2013-07-23  4:12 Stephen Rothwell
2013-07-23  4:12 ` Stephen Rothwell

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=877elmhvf9.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.