From: Antonio Ospite <ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
To: Bastien Nocera <hadess-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
Cc: linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cbe-oss-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Jiri Kosina <jkosina-AlSwsSmVLrQ@public.gmane.org>
Subject: Re: [PATCH 1/2] hid/hid-sony: Apply sixaxis quirks only to sixaxis
Date: Wed, 1 Sep 2010 19:20:55 +0200 [thread overview]
Message-ID: <20100901192055.2f23c8c7.ospite@studenti.unina.it> (raw)
In-Reply-To: <1283357615.2361.20.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
On Wed, 01 Sep 2010 17:13:35 +0100
Bastien Nocera <hadess-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org> wrote:
> On Mon, 2010-05-03 at 22:15 +0200, Antonio Ospite wrote:
> > Be more explicit and avoid calling sony_set_operational_usb() when we
> > have USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE.
> >
> > While at it, rename the sony_set_operational routines to
> > sixaxis_set_operational as they are sixaxis specific.
> >
> > This is also in preparation for the sysfs interface to set and get bdaddr
> > over usb and for some other Sixaxis report fixup.
> >
> > Signed-off-by: Antonio Ospite <ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
>
> Signed-off-by: Bastien Nocera <hadess-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
>
Thanks Bastien for bringing this up again, I was going to repost
this patch sometime this month.
Added Jiri to CC as I forgot to do that back then.
Regards,
Antonio
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-01 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 20:15 [PATCH 0/2] Groundwork for Sixaxis paring into bluez Antonio Ospite
2010-05-03 20:15 ` [PATCH 1/2] hid/hid-sony: Apply sixaxis quirks only to sixaxis Antonio Ospite
[not found] ` <1272917756-31098-2-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2010-09-01 16:13 ` Bastien Nocera
[not found] ` <1283357615.2361.20.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-09-01 17:20 ` Antonio Ospite [this message]
2010-09-02 7:41 ` Jiri Kosina
2010-09-03 18:01 ` Antonio Ospite
[not found] ` <1272917756-31098-1-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2010-05-03 20:15 ` [PATCH 2/2] hid/hid-sony: get and set Sixaxis bdaddr via sysfs Antonio Ospite
[not found] ` <1272917756-31098-3-git-send-email-ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
2010-09-01 16:17 ` Bastien Nocera
2010-09-01 17:28 ` Antonio Ospite
2010-09-01 17:41 ` Bastien Nocera
2010-05-20 9:05 ` [PATCH 0/2] Groundwork for Sixaxis paring into bluez Antonio Ospite
2010-05-12 13:12 ` Antonio Ospite
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=20100901192055.2f23c8c7.ospite@studenti.unina.it \
--to=ospite-anj+ml1zbip93qaqavx+gl6hyfs7nttn@public.gmane.org \
--cc=cbe-oss-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=hadess-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org \
--cc=jkosina-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).