public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/6] Broadcom defconfig-arm64 changes for 4.19
Date: Sat, 14 Jul 2018 14:10:12 -0700	[thread overview]
Message-ID: <20180714211012.mh3j7v7bdnlpnenw@localhost> (raw)
In-Reply-To: <20180709153035.6376-2-f.fainelli@gmail.com>

On Mon, Jul 09, 2018 at 08:30:31AM -0700, Florian Fainelli wrote:
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
> 
>   Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
> 
> are available in the git repository at:
> 
>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.19/defconfig-arm64
> 
> for you to fetch changes up to ec93d5a25f9f959e6c20351e74182ad4bfa85716:
> 
>   Merge tag 'bcm2835-defconfig-64-next-2018-07-03' into defconfig-arm64/next (2018-07-09 05:23:47 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM64-based SoCs defconfig changes
> for 4.19, please pull the following changes:
> 
> - Stefan enables the Raspberry Pi voltage sensor driver (HWMON) in the
>   arm64 defconfig file
> 
> ----------------------------------------------------------------
> Florian Fainelli (1):
>       Merge tag 'bcm2835-defconfig-64-next-2018-07-03' into defconfig-arm64/next
> 
> Stefan Wahren (1):
>       arm64: defconfig: Enable RPi voltage sensor

It looks like you revisited this tag and branch after you sent the pull
request. It's usually better to do a new tag instead (and remove the
old one in case you don't want me to merge it), to avoid confusion.

New contents looks reasonable so I merged anyway.


-Olof

  reply	other threads:[~2018-07-14 21:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 15:30 [GIT PULL 1/6] Broadcom defconfig changes for 4.19 Florian Fainelli
2018-07-09 15:30 ` [GIT PULL 2/6] Broadcom defconfig-arm64 " Florian Fainelli
2018-07-14 21:10   ` Olof Johansson [this message]
2018-07-16  9:24     ` Florian Fainelli
2018-07-09 15:30 ` [GIT PULL 3/6] Broadcom devicetree " Florian Fainelli
2018-07-14 21:11   ` Olof Johansson
2018-07-09 15:30 ` [GIT PULL 4/6] Broadcom devicetree-arm64 " Florian Fainelli
2018-07-14 21:11   ` Olof Johansson
2018-07-09 15:30 ` [GIT PULL 5/6] Broadcom drivers " Florian Fainelli
2018-07-09 17:49   ` Florian Fainelli
2018-07-14 21:15     ` Olof Johansson
2018-07-09 15:30 ` [GIT PULL 6/6] Broadcom soc " Florian Fainelli
2018-07-14 21:12   ` Olof Johansson
2018-07-14 21:08 ` [GIT PULL 1/6] Broadcom defconfig " Olof Johansson

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=20180714211012.mh3j7v7bdnlpnenw@localhost \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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