All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Tissoires <tissoire@cena.fr>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Michael Poole <mdpoole@troilus.org>,
	linux-input@vger.kernel.org, Stephane Chatty <chatty@enac.fr>
Subject: Re: [PATCH 3/3] HID: deletion of unused code in hid-magicmouse.
Date: Wed, 10 Mar 2010 16:39:51 +0100	[thread overview]
Message-ID: <4B97BD47.5050004@cena.fr> (raw)
In-Reply-To: <alpine.LNX.2.00.1003101607560.18642@pobox.suse.cz>

No problem, this patch had a meaning only with the 2 others Micheal 
already reviewed.

The core idea of the series of patch was to register the fields in the 
newly created report in order to having two benefits:
- use the input created by hid-input (not required anymore as you 
integrated Michael's patch) and suppress the second input created by 
hand (this is why the patch n°3 named "HID: deletion of unused code in 
hid-magicmouse" suppress everything related to this input)
- recreate the fields in the report descriptor in order to avoid using 
the raw event in a later patch.

I have now to look on how can we register fields in a report that are 
non mandatory. Michael told me that he did not found it too.
After that, I will probably resend a better patch.

Cheers,
Benjamin


Le 10/03/2010 16:09, Jiri Kosina a écrit :
> On Mon, 8 Mar 2010, Benjamin Tissoires wrote:
>
>>> Well ... I don't see any patch titled "HID: deletion of unused code in
>>> hid-magicmouse" neither in my inbox nor in my linux-input@ folder. Could
>>> you perhaps please resend?
>>>
>>> Thanks,
>>
>> Of course, I attached it. Do I need to send it in mbox format or is it ok ?
>
> Well, magicmouse_setup_input() is actually used from inside the probe
> routine, so we'd rather not remove it.
>
> I have already merged Michael's patch with calls hid_hw_start() with
> HID_CONNECT_HIDINPUT flag cleared out, so the registration of the input
> device is now performed properly.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-03-10 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1268065277-30129-1-git-send-email-tissoire@cena.fr>
     [not found] ` <1268065277-30129-2-git-send-email-tissoire@cena.fr>
     [not found]   ` <1268065277-30129-3-git-send-email-tissoire@cena.fr>
     [not found]     ` <1268065277-30129-4-git-send-email-tissoire@cena.fr>
     [not found]       ` <1268065277-30129-5-git-send-email-tissoire@cena.fr>
2010-03-08 16:27         ` [PATCH 3/3] HID: deletion of unused code in hid-magicmouse Benjamin Tissoires
2010-03-08 16:30           ` Jiri Kosina
2010-03-08 16:57             ` Benjamin Tissoires
2010-03-08 20:27               ` Michael Poole
2010-03-08 20:51                 ` Benjamin Tissoires
2010-03-08 23:56                   ` Jiri Kosina
2010-03-09 12:00                     ` Rantanplan
2010-03-10 15:09               ` Jiri Kosina
2010-03-10 15:39                 ` Benjamin Tissoires [this message]
2010-03-08 21:29 Benjamin Tissoires

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=4B97BD47.5050004@cena.fr \
    --to=tissoire@cena.fr \
    --cc=chatty@enac.fr \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=mdpoole@troilus.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.