From: Geoff Levand <geoffrey.levand@am.sony.com>
To: "Ruslan N. Marchenko" <rufferson@gmail.com>
Cc: linux-bluetooth@vger.kernel.org,
Bastien Nocera <hadess@hadess.net>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: PATCH for input/fakehid.c to fix PS3 remote unpairing
Date: Wed, 26 Aug 2009 16:46:17 -0700 [thread overview]
Message-ID: <4A95C949.6080707@am.sony.com> (raw)
In-Reply-To: <a70b8cd30908251339h1bf0bdefye7ac669fafd57f51@mail.gmail.com>
On 08/25/2009 01:39 PM, Ruslan N. Marchenko wrote:
> Ehm... Have I missed something? Should I post it immediately in commit
> form? I just want it to be reviewed before actual commit %\
If you just want a review, put 'RFC' into the subject
line of your mail, maybe something like this:
'[RFC] Fix PS3 remote unpairing'.
-Geoff
next prev parent reply other threads:[~2009-08-26 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 16:10 PATCH for input/fakehid.c to fix PS3 remote unpairing Ruslan N. Marchenko
2009-08-19 16:16 ` Bastien Nocera
2009-08-22 20:03 ` Marcel Holtmann
2009-08-24 21:06 ` Ruslan N. Marchenko
2009-08-25 20:39 ` Ruslan N. Marchenko
2009-08-26 23:46 ` Geoff Levand [this message]
2009-08-22 20:02 ` Marcel Holtmann
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=4A95C949.6080707@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=rufferson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox