From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] bcm2835-defconfig-next-2020-03-27
Date: Fri, 27 Mar 2020 22:16:32 +0100 [thread overview]
Message-ID: <20200327211632.32346-3-nsaenzjulienne@suse.de> (raw)
In-Reply-To: <20200327211632.32346-1-nsaenzjulienne@suse.de>
Hi Florian,
The following changes since commit 8068b7b63583764b46416a62856e42fb1f954ab6:
Merge tag 'tags/bcm2835-defconfig-next-2020-03-09' into defconfig/next (2020-03-10 11:13:21 -0700)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git tags/bcm2835-defconfig-next-2020-03-27
for you to fetch changes up to f06f924a65fb3991614fb23a783d4fef9c8d14ea:
ARM: bcm2835_defconfig: Enable fixed-regulator (2020-03-27 21:27:47 +0100)
----------------------------------------------------------------
Enables fixed regulator in bcm2835_defconfig
----------------------------------------------------------------
Nicolas Saenz Julienne (1):
ARM: bcm2835_defconfig: Enable fixed-regulator
arch/arm/configs/bcm2835_defconfig | 1 +
1 file changed, 1 insertion(+)
next prev parent reply other threads:[~2020-03-27 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 21:16 [GIT PULL 1/3] bcm2835-dt-fixes-2020-03-27 Nicolas Saenz Julienne
2020-03-27 21:16 ` [GIT PULL 2/3] bcm2835-dt-next-2020-03-27 Nicolas Saenz Julienne
2020-04-04 21:36 ` Florian Fainelli
2020-03-27 21:16 ` Nicolas Saenz Julienne [this message]
2020-04-04 21:37 ` [GIT PULL 3/3] bcm2835-defconfig-next-2020-03-27 Florian Fainelli
2020-04-01 19:38 ` [GIT PULL 1/3] bcm2835-dt-fixes-2020-03-27 Florian Fainelli
2020-04-01 19:46 ` Nicolas Saenz Julienne
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=20200327211632.32346-3-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-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;
as well as URLs for NNTP newsgroup(s).