linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 20
Date: Tue, 20 Apr 2021 15:35:37 +0300	[thread overview]
Message-ID: <YH7KmRQV2oD7fooj@smile.fi.intel.com> (raw)
In-Reply-To: <YH7G235DGG6bEDTF@smile.fi.intel.com>

On Tue, Apr 20, 2021 at 03:19:39PM +0300, Andy Shevchenko wrote:
> On Tue, Apr 20, 2021 at 03:02:51PM +0300, Andy Shevchenko wrote:
> > On Tue, Apr 20, 2021 at 07:47:18PM +1000, Stephen Rothwell wrote:

...

> > I have full of build warnings / errors in x86 and iommu

Found the culprit -- it was uncleaned stuff from the other build in the source
tree. So, it was only me who experienced that :-)

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-04-20 12:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  9:47 linux-next: Tree for Apr 20 Stephen Rothwell
2021-04-20 12:02 ` Andy Shevchenko
2021-04-20 12:19   ` Andy Shevchenko
2021-04-20 12:35     ` Andy Shevchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-20 15:44 broonie
2022-04-20  7:50 Stephen Rothwell
2020-04-20  4:26 Stephen Rothwell
2020-04-20  7:14 ` Christian Borntraeger
2020-04-20  7:23   ` Hadar Gat
2020-04-20  7:30     ` Christian Borntraeger
2020-04-20  7:25   ` Stephen Rothwell
2018-04-20  6:11 Stephen Rothwell
2017-04-20  6:43 Stephen Rothwell
2016-04-20  5:12 Stephen Rothwell
2015-04-20  5:45 Stephen Rothwell
2012-04-20  5:51 Stephen Rothwell

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=YH7KmRQV2oD7fooj@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).