From: Tony Lindgren <tony@atomide.com>
To: Rong Chen <rong.a.chen@intel.com>
Cc: "kernel test robot" <lkp@intel.com>,
"Adam Ford" <aford173@gmail.com>,
linux-omap@vger.kernel.org, kbuild-all@lists.01.org,
aford@beaconembedded.com,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Paul Walmsley" <paul@pwsan.com>,
"Russell King" <linux@armlinux.org.uk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2
Date: Wed, 1 Jul 2020 07:44:15 -0700 [thread overview]
Message-ID: <20200701144415.GH37466@atomide.com> (raw)
In-Reply-To: <c30dd2e4-0f80-9caf-0cfa-45a60a2d1319@intel.com>
* Rong Chen <rong.a.chen@intel.com> [200630 00:31]:
>
>
> On 6/30/20 2:12 AM, Tony Lindgren wrote:
> > * kernel test robot <lkp@intel.com> [200617 17:28]:
> > > Hi Adam,
> > >
> > > Thank you for the patch! Yet something to improve:
> > >
> > > [auto build test ERROR on omap/for-next]
> > > [cannot apply to balbi-usb/testing/next]
> > > [if your patch is applied to the wrong git tree, please drop us a note to help
> > > improve the system. BTW, we also suggest to use '--base' option to specify the
> > > base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
> > This applies to v5.8-rc1, so the error above can be ignored now.
> >
> > Applying patch into omap-for-v5.9/ti-sysc-drop-pdata.
>
> Hi Tony,
>
> Thanks for the feedback, we'll fix the wrong base.
OK thanks. Not sure what you use to determine the base, but in
general current Linux mainline master or for-next should work
as the base.
Regards,
Tony
prev parent reply other threads:[~2020-07-01 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 10:58 [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2 Adam Ford
2020-06-17 17:26 ` kernel test robot
2020-06-29 18:12 ` Tony Lindgren
2020-06-30 0:29 ` [kbuild-all] " Rong Chen
2020-07-01 14:44 ` Tony Lindgren [this message]
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=20200701144415.GH37466@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=paul@pwsan.com \
--cc=robh+dt@kernel.org \
--cc=rong.a.chen@intel.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 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).