All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 4/4] defconfig changes for omaps for v4.16
Date: Thu, 4 Jan 2018 23:07:49 -0800	[thread overview]
Message-ID: <20180105070749.ce46d5r76k632gh3@localhost> (raw)
In-Reply-To: <pull-1513966338-859035@atomide.com-4>

On Fri, Dec 22, 2017 at 10:14:27AM -0800, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
> 
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
> 
>   Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.16/defconfig-signed
> 
> for you to fetch changes up to d03366dcbffcc3754f9f8a1d8ae74f438312e07d:
> 
>   ARM: multi_v7_defconfig: Enable CONFIG_PCI_DRA7XX (Host & Device modes) (2017-12-21 07:12:44 -0800)

Merged, thanks.


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] defconfig changes for omaps for v4.16
Date: Thu, 4 Jan 2018 23:07:49 -0800	[thread overview]
Message-ID: <20180105070749.ce46d5r76k632gh3@localhost> (raw)
In-Reply-To: <pull-1513966338-859035@atomide.com-4>

On Fri, Dec 22, 2017 at 10:14:27AM -0800, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
> 
> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
> 
>   Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.16/defconfig-signed
> 
> for you to fetch changes up to d03366dcbffcc3754f9f8a1d8ae74f438312e07d:
> 
>   ARM: multi_v7_defconfig: Enable CONFIG_PCI_DRA7XX (Host & Device modes) (2017-12-21 07:12:44 -0800)

Merged, thanks.


-Olof

  reply	other threads:[~2018-01-05  7:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 18:14 [GIT PULL 1/4] soc changes for omaps for v4.16, part 2 Tony Lindgren
2017-12-22 18:14 ` Tony Lindgren
2017-12-22 18:14 ` [GIT PULL 2/4] driver changes for ti-sysc for v4.16 Tony Lindgren
2017-12-22 18:14   ` Tony Lindgren
2018-01-05  7:06   ` Olof Johansson
2018-01-05  7:06     ` Olof Johansson
2017-12-22 18:14 ` [GIT PULL 3/4] dts changes for omaps for v4.16, part 2 Tony Lindgren
2017-12-22 18:14   ` Tony Lindgren
2017-12-22 18:55   ` Tony Lindgren
2017-12-22 18:55     ` Tony Lindgren
2017-12-23 16:29     ` Tony Lindgren
2017-12-23 16:29       ` Tony Lindgren
2018-01-05  7:06       ` Olof Johansson
2018-01-05  7:06         ` Olof Johansson
2017-12-22 18:14 ` [GIT PULL 4/4] defconfig changes for omaps for v4.16 Tony Lindgren
2017-12-22 18:14   ` Tony Lindgren
2018-01-05  7:07   ` Olof Johansson [this message]
2018-01-05  7:07     ` Olof Johansson
2018-01-05  6:59 ` [GIT PULL 1/4] soc changes for omaps for v4.16, part 2 Olof Johansson
2018-01-05  6:59   ` Olof Johansson
2018-01-05 18:20   ` Tony Lindgren
2018-01-05 18:20     ` Tony Lindgren

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=20180105070749.ce46d5r76k632gh3@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 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.