All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Colenbrander, Roelof" <Roderick.Colenbrander@sony.com>
Cc: "dh.herrmann@googlemail.com" <dh.herrmann@googlemail.com>,
	"jikos@kernel.org" <jikos@kernel.org>,
	"benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"roderick@gaikai.com" <roderick@gaikai.com>
Subject: Re: [PATCH] HID: uhid: Fixes a bug with userspace bluetooth stacks, which causes hangs during certain operations
Date: Tue, 31 May 2016 14:59:07 -0700	[thread overview]
Message-ID: <20160531215907.GB30197@kroah.com> (raw)
In-Reply-To: <1DD62093774CEE42AFC16E785A1088045F496A74@USCULXMSG04.am.sony.com>

On Tue, May 31, 2016 at 09:10:36PM +0000, Colenbrander, Roelof wrote:
> Hi,
> 
> The patch in this thread is part of input work I'm doing with my team
> and will hopefully be the first of many, but we are new to the
> linux-input project. We shared this patch first in April and again
> about 2 weeks ago in May, but we haven't received any feedback so far.

It's been the middle of the merge window for the past 2 weeks, where no
new code is usually reviewed or handled at all.  Give the maintainers a
bit of time to catch up.

thanks,

greg k-h

  reply	other threads:[~2016-05-31 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 20:11 [PATCH] HID: uhid: Fixes a bug with userspace bluetooth stacks, which causes hangs during certain operations Roderick Colenbrander
2016-05-31 21:10 ` Colenbrander, Roelof
2016-05-31 21:10   ` Colenbrander, Roelof
2016-05-31 21:59   ` Greg KH [this message]
2016-06-01 14:26 ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2016-04-21 20:54 roderick
2016-04-21 21:15 ` kbuild test robot
2016-04-21 21:15 ` kbuild test robot
2016-04-21 21:27   ` Roderick Colenbrander

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=20160531215907.GB30197@kroah.com \
    --to=greg@kroah.com \
    --cc=Roderick.Colenbrander@sony.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dh.herrmann@googlemail.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roderick@gaikai.com \
    --cc=stable@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 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.