From: Benjamin Tissoires <benjamin.tissoires@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 6 (hid)
Date: Thu, 7 Mar 2013 12:20:52 +0100 [thread overview]
Message-ID: <CAN+gG=GftPSHEbrsFkjQdCdGeRXQvDU-=c7bhBxK9n5YRQe2iQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1303071130520.28677@pobox.suse.cz>
On Thu, Mar 7, 2013 at 11:33 AM, Jiri Kosina <jkosina@suse.cz> wrote:
> On Thu, 7 Mar 2013, Benjamin Tissoires wrote:
>
>> You should have at least one other patch for hid-mt:
>> https://patchwork.kernel.org/patch/2193641/
>
> Ah, right, that one is in my queue as well, sorry for not mentioning it in
> my previous post.
No problems :)
>
> That doesn't remove the direct call either though.
true
>
>> And I sent as a RFC the patch I was talking about:
>> https://patchwork.kernel.org/patch/2193801/
>> https://patchwork.kernel.org/patch/2193821/
>>
>> These two RFCs have been reviewed by David Herrmann, so maybe we can
>> include them in their current form as no one else complained about it
>> ( maybe you will :) ).
>
> For some reason these two vanished between the cracks of my mailbox.
> Thanks for pointing those out, I will process them today and either apply
> it, or fix it for -next by adding a config dependency.
>
ok, thanks for dealing with it.
Cheers,
Benjamin
prev parent reply other threads:[~2013-03-07 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 0:50 linux-next: Tree for Mar 6 Stephen Rothwell
2013-03-06 19:26 ` linux-next: Tree for Mar 6 (hid) Randy Dunlap
2013-03-07 8:13 ` Benjamin Tissoires
2013-03-07 10:09 ` Jiri Kosina
2013-03-07 10:28 ` Benjamin Tissoires
2013-03-07 10:33 ` Jiri Kosina
2013-03-07 11:20 ` Benjamin Tissoires [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='CAN+gG=GftPSHEbrsFkjQdCdGeRXQvDU-=c7bhBxK9n5YRQe2iQ@mail.gmail.com' \
--to=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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 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).