From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jeremiah Mahler <jmmahler@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 10
Date: Wed, 10 Dec 2014 17:27:36 -0500 [thread overview]
Message-ID: <20141210222736.GA19788@kroah.com> (raw)
In-Reply-To: <20141211075142.5fe2993a@canb.auug.org.au>
On Thu, Dec 11, 2014 at 07:51:42AM +1100, Stephen Rothwell wrote:
> Hi Jeremiah,
>
> On Wed, 10 Dec 2014 03:30:14 -0800 Jeremiah Mahler <jmmahler@gmail.com> wrote:
> >
> > Just a FYI.
> >
> > As of -next 20141210 commit d32394fae95741d733b174ec1446f27765f80233,
> > which caused a suspend hang bug [1], is still in the tree. Greg created
> > a revert patch for it in driver-core [2] but I am not sure if this will
> > make its way to -next.
> >
> > [1]: https://lkml.org/lkml/2014/12/3/215
> >
> > [2]: https://git.kernel.org/cgit/linux/kernel/git/gregkh/driver-core.git/commit/?h=driver-core-testing&id=f1c488a78d9f1a22cdb15648c15e70fd82ed229a
>
> Unfortunately, I can't control how often maintainers update the
> versions of their trees that are included in linux-next :-(
Oops, sorry about that, with travel this week, I forgot to push that one
out to the git.kernel.org, my fault. Now done.
greg k-h
next prev parent reply other threads:[~2014-12-10 22:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 9:48 linux-next: Tree for Dec 10 Stephen Rothwell
2014-12-10 11:30 ` Jeremiah Mahler
2014-12-10 20:51 ` Stephen Rothwell
2014-12-10 22:27 ` Greg KH [this message]
2014-12-10 22:34 ` Jeremiah Mahler
-- strict thread matches above, loose matches on Subject: below --
2025-12-10 2:57 Stephen Rothwell
2024-12-10 5:26 Stephen Rothwell
2021-12-10 21:39 broonie
2020-12-10 10:12 Stephen Rothwell
2019-12-10 3:02 Stephen Rothwell
2018-12-10 9:15 Stephen Rothwell
2015-12-10 5:53 Stephen Rothwell
2013-12-10 4:23 Stephen Rothwell
2013-12-10 4:23 ` Stephen Rothwell
2012-12-10 9:19 Stephen Rothwell
2012-12-10 9:19 ` 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=20141210222736.GA19788@kroah.com \
--to=greg@kroah.com \
--cc=jmmahler@gmail.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 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.