From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Olof Johansson <olof@lixom.net>
Cc: linux-unisoc@lists.infradead.org, arm@kernel.org, arnd@arndb.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Bitmain changes for v5.2
Date: Mon, 29 Apr 2019 10:35:48 +0530 [thread overview]
Message-ID: <20190429050548.GA2384@Mani-XPS-13-9360> (raw)
In-Reply-To: <20190428195631.qexzfws3uj66fgr2@localhost>
Hi Olof,
On Sun, Apr 28, 2019 at 12:56:31PM -0700, Olof Johansson wrote:
> Hi Mani,
>
>
> On Tue, Apr 23, 2019 at 09:07:20PM +0530, Manivannan Sadhasivam wrote:
> > Hi Arnd, Olof,
> >
> > Please consider pulling the Bitmain SoC changes for v5.2. For this
> > cycle only couple of dts changes are added and the details are in
> > signed tag.
> >
> > Thanks,
> > Mani
> >
> > ---
> >
> > The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
> >
> > Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
>
> Unfortunately you based your branch on a very recent -rc. We always strive to
> keep most new branches based on older -rcs, to avoid polluting our tree with
> repeated back-merges of mainline to make diffstats easier to parse.
>
Sorry, I'm not aware of that!
> Would you mind respinning this with -rc3 or so as a base? Thanks!
>
Sure, I'll send a PR with -rc3 as a base.
Thanks,
Mani
>
> -Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-29 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 15:37 [GIT PULL] Bitmain changes for v5.2 Manivannan Sadhasivam
2019-04-28 19:56 ` Olof Johansson
2019-04-29 5:05 ` Manivannan Sadhasivam [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-29 5:43 Manivannan Sadhasivam
2019-04-29 17:06 ` 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=20190429050548.GA2384@Mani-XPS-13-9360 \
--to=manivannan.sadhasivam@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-unisoc@lists.infradead.org \
--cc=olof@lixom.net \
/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).