Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Olof Johansson <olof@lixom.net>
To:     torvalds@linux-foundation.org
Cc:     linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        arm@kernel.org, soc@kernel.org
Subject: [GIT PULL 0/5 v2] ARM: SoC contents for 5.6
Date:   Sat,  8 Feb 2020 13:25:28 -0800
Message-Id: <20200208212533.30744-1-olof@lixom.net>
In-Reply-To: <20200208112018.29819-1-olof@lixom.net>
References: <20200208112018.29819-1-olof@lixom.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Linus,

I completely botched the last generation of pull requests by
mis-generating them, and I also missed to push the tags to the server.

Here's the fresh set. Apologies for the noise, please merge.


For anyone keeping track at home, what happened at my end was:

We use a script to generate our pull requests, and it's ran against a tree
that is mainline + the merged branches. The flow is usually to merge in
a branch, note down any conflicts needing to be resolved, then generate
the pull request. Or, sometimes, I do all the merges and then generate the
last pull request, reset the tree to HEAD~, second-last pull request, etc.

I completely missed changing the tree between the generation this time,
so every pull request referenced the right tag, but the diffstat and
other contents was botched.

It's probably time to automate more of this with scripts at my end,
to avoid these manual mistakes.


-Olof