From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Guenter Roeck <linux@roeck-us.net>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@kernel.org>
Subject: Re: linux-next: Tree for Feb 12
Date: Sat, 13 Feb 2016 16:50:28 +0100 [thread overview]
Message-ID: <20160213155028.GA17704@pd.tnic> (raw)
In-Reply-To: <CALCETrUWRJR5=4sXsg=KYX6mYRrXkvXSOgccX+PVQa7dHXQYxw@mail.gmail.com>
On Sat, Feb 13, 2016 at 06:57:24AM -0800, Andy Lutomirski wrote:
> I think Borislav's patch should fix this.
Yeah, guys, can you give it a try:
https://lkml.kernel.org/r/20160210145116.GF23914@pd.tnic
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-02-13 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 5:20 linux-next: Tree for Feb 12 Stephen Rothwell
2016-02-12 6:02 ` Sudip Mukherjee
2016-02-13 7:49 ` Guenter Roeck
2016-02-13 14:57 ` Andy Lutomirski
2016-02-13 15:50 ` Borislav Petkov [this message]
2016-02-13 18:55 ` Sudip Mukherjee
[not found] ` <20160212162035.1e0260cd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2016-02-12 14:27 ` Sudip Mukherjee
2016-02-12 14:27 ` Sudip Mukherjee
-- strict thread matches above, loose matches on Subject: below --
2026-02-12 14:49 Mark Brown
2025-02-12 5:33 Stephen Rothwell
2024-02-12 4:31 Stephen Rothwell
2021-02-12 11:07 Stephen Rothwell
2020-02-12 2:58 Stephen Rothwell
2019-02-12 6:50 Stephen Rothwell
2018-02-12 2:46 Stephen Rothwell
2015-02-12 6:07 Stephen Rothwell
2014-02-12 5:47 Stephen Rothwell
2014-02-12 5:47 ` Stephen Rothwell
2013-02-12 5:09 Stephen Rothwell
2013-02-12 5:09 ` 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=20160213155028.GA17704@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@gmail.com \
/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.