From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression in next caused by 95026658c46e i2c: do not use internal..
Date: Mon, 14 Mar 2016 17:52:06 +0100 [thread overview]
Message-ID: <20160314165206.GA16371@katana> (raw)
In-Reply-To: <20160314160944.GG9329@atomide.com>
Hi,
> Having something like this happen just as the merge window opens is
> not nice. You guys should already know..
I already applied the fix.
> The patches in next should be sitting there for a few weeks before the
> merge window so issues like this are found out early.
I understand this was a major hickup and I am sorry for this. I should
have known better.
I am not taking 100% of the blame, though: The amount of submissions is
rising faster than the amount of non-maintainer review being done (at
least in the subsystems I work on). I took a wrong step in trying to
handle the gap. I am really sorry about the fuzz, yet I can't deny there
is also something inevitable in that to me. That being said, I'll of
course try harder to not let this happen again.
Regards,
Wolfram
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160314/4f3c058b/attachment.sig>
next prev parent reply other threads:[~2016-03-14 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 16:09 Regression in next caused by 95026658c46e i2c: do not use internal Tony Lindgren
2016-03-14 16:52 ` Wolfram Sang [this message]
2016-03-14 17:26 ` Tony Lindgren
2016-03-14 17:35 ` Sudip Mukherjee
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=20160314165206.GA16371@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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).