All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, arm@kernel.org
Subject: [GIT PULL 0/4] ARM: SoC changes for v4.21
Date: Mon, 31 Dec 2018 13:46:36 -0800	[thread overview]
Message-ID: <20181231214640.17015-1-olof@lixom.net> (raw)

Hi Linus,

Here's the batch of changes for arm-soc for this merge window. It's
arriving later than I had planned for, the holidays messed up schedules
and time availability a lot at my end this year.

As for the material itself, it's pretty straight forward. The only
branch with conflicts is the SoC one, I mention in that email how to
resolve them. Most of the new material is in the DT branch (as always),
and that pull request also contains the overview of new platforms, etc.

In addition to this we have a branch with some late-merged material that
I'm letting sit for a few days and might send in towards the end of the
merge window if things have been going smoothly.


Thanks,

-Olof


WARNING: multiple messages have this Message-ID
From: Olof Johansson <olof@lixom.net>
To: torvalds@linux-foundation.org
Cc: arm@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/4] ARM: SoC changes for v4.21
Date: Mon, 31 Dec 2018 13:46:36 -0800	[thread overview]
Message-ID: <20181231214640.17015-1-olof@lixom.net> (raw)

Hi Linus,

Here's the batch of changes for arm-soc for this merge window. It's
arriving later than I had planned for, the holidays messed up schedules
and time availability a lot at my end this year.

As for the material itself, it's pretty straight forward. The only
branch with conflicts is the SoC one, I mention in that email how to
resolve them. Most of the new material is in the DT branch (as always),
and that pull request also contains the overview of new platforms, etc.

In addition to this we have a branch with some late-merged material that
I'm letting sit for a few days and might send in towards the end of the
merge window if things have been going smoothly.


Thanks,

-Olof


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2018-12-31 21:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31 21:46 Olof Johansson [this message]
2018-12-31 21:46 ` Olof Johansson
2018-12-31 21:46 ` [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot
2019-01-01  1:45     ` pr-tracker-bot
2018-12-31 21:46 ` [GIT PULL 2/4] ARM: SoC driver updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot
2019-01-01  1:45     ` pr-tracker-bot
2018-12-31 21:46 ` [GIT PULL 3/4] ARM: Device-tree updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot
2019-01-01  1:45     ` pr-tracker-bot
2018-12-31 21:46 ` [GIT PULL 4/4] ARM: SoC defconfig updates Olof Johansson
2018-12-31 21:46   ` Olof Johansson
2019-01-01  1:45   ` pr-tracker-bot
2019-01-01  1:45     ` pr-tracker-bot

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=20181231214640.17015-1-olof@lixom.net \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL 0/4] ARM: SoC changes for v4.21' \
    /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

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.