linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mark Brown <broonie@kernel.org>
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 Dec 14
Date: Wed, 15 Dec 2021 20:40:11 +0200	[thread overview]
Message-ID: <Ybo2i0lmD2kx/cg6@smile.fi.intel.com> (raw)
In-Reply-To: <Yboui5aym4eB6oP8@sirena.org.uk>

On Wed, Dec 15, 2021 at 06:06:03PM +0000, Mark Brown wrote:
> On Wed, Dec 15, 2021 at 05:54:55PM +0200, Andy Shevchenko wrote:

> > The other issue I have noticed is that gpio-intel branches [1] are out of the
> > merge. I haven't got any email about any issues with them.
> 
> > Do you have the latest and greatest list of repositories to merge?
> 
> You can see in the merge log that it's getting skipped due to an issue
> with the previous tree (which also has a build failure causing me to
> need to revert it) upsetting the script.

Yes, I see now. But as far as I know my repo doesn't have issues (neither
compilation nor merge), or at least nobody so far informed me about.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-12-15 18:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 22:32 linux-next: Tree for Dec 14 broonie
2021-12-15  0:37 ` Nathan Chancellor
2021-12-15  1:49 ` linux-next: Tree for Dec 14 (arch/x86/kernel/apic/msi.o) Randy Dunlap
2021-12-15 19:25   ` Thomas Gleixner
2021-12-15 15:54 ` linux-next: Tree for Dec 14 Andy Shevchenko
2021-12-15 18:06   ` Mark Brown
2021-12-15 18:40     ` Andy Shevchenko [this message]
2021-12-15 18:43       ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2023-12-14  5:33 Stephen Rothwell
2022-12-14  3:21 Stephen Rothwell
2020-12-14 10:20 Stephen Rothwell
2018-12-14  7:18 Stephen Rothwell
2018-12-15 15:51 ` Guenter Roeck
2017-12-14  7:06 Stephen Rothwell
2016-12-14  4:22 Stephen Rothwell
2016-12-14 16:25 ` Paul Gortmaker
2016-12-14 20:07   ` Heiko Carstens
2015-12-14  6:18 Stephen Rothwell
2012-12-14  7:42 Stephen Rothwell
2011-12-14  7:26 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=Ybo2i0lmD2kx/cg6@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).