From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jarod Wilson <jarod@redhat.com>
Cc: Valdis.Kletnieks@vt.edu,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: mmotm 2010-07-19-16-37 uploaded
Date: Sun, 25 Jul 2010 15:00:05 -0300 [thread overview]
Message-ID: <4C4C7BA5.3050709@redhat.com> (raw)
In-Reply-To: <20100720214112.GM13176@redhat.com>
Em 20-07-2010 18:41, Jarod Wilson escreveu:
> On Tue, Jul 20, 2010 at 05:11:40PM -0400, Valdis.Kletnieks@vt.edu wrote:
>> On Tue, 20 Jul 2010 13:50:27 PDT, Dmitry Torokhov said:
>>
>>>> And things go downhill from there...
>>>
>>> I guess you need these 2 from Jarod...
>>
>> Hmm. I seem to remember 2 similar patches from the last time I reported it. :)
>>
>> System boots fine after applying those two patches. I'll let somebody else
>> worry about making sure they end up in linux-next in time for the next merge
>> window...
>
> I believe Mauro's on vacation at the moment, but due back Real Soon Now,
> and I'd expect him to pick up both fixes shortly after he settles back in
> at his desk, so they should be in next before much longer, and definitely
> before the merge window.
I just arrived from vacations. I'll be testing this patch and applying it if OK.
Just give me some days, since I have a huge backlog due to vacations.
Cheers,
Mauro.
prev parent reply other threads:[~2010-07-25 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201007200007.o6K07Xbg028863@imap1.linux-foundation.org>
2010-07-20 20:41 ` mmotm 2010-07-19-16-37 uploaded Valdis.Kletnieks
2010-07-20 20:38 ` Jarod Wilson
[not found] ` <201007201350.28961.dmitry.torokhov@gmail.com>
2010-07-20 21:11 ` Valdis.Kletnieks
2010-07-20 21:41 ` Jarod Wilson
2010-07-25 18:00 ` Mauro Carvalho Chehab [this message]
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=4C4C7BA5.3050709@redhat.com \
--to=mchehab@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jarod@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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).