From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
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 18:06:03 +0000 [thread overview]
Message-ID: <Yboui5aym4eB6oP8@sirena.org.uk> (raw)
In-Reply-To: <YboPz454GCe6ZA7g@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Wed, Dec 15, 2021 at 05:54:55PM +0200, Andy Shevchenko wrote:
Please note that due to people replying with random bug reports against
the actual code in -next replying to the -next message isn't a super
good way of getting my attention you can get lost in the noise.
> Thanks, I see tags now.
I fixed the bug with the script, it doesn't check for errors when
tagging unfortunately.
> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-15 18:06 UTC|newest]
Thread overview: 21+ 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 [this message]
2021-12-15 18:40 ` Andy Shevchenko
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
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=Yboui5aym4eB6oP8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.