From: Benjamin Tissoires <tissoire@tls.cena.fr>
To: Michael Poole <mdpoole@troilus.org>
Cc: Benjamin Tissoires <tissoire@cena.fr>,
Jiri Kosina <jkosina@suse.cz>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, Stephane Chatty <chatty@enac.fr>
Subject: Re: [PATCH 3/3] HID: deletion of unused code in hid-magicmouse.
Date: Mon, 08 Mar 2010 21:51:36 +0100 [thread overview]
Message-ID: <4B956358.80608@tls.cena.fr> (raw)
In-Reply-To: <87sk8a36f4.fsf@troilus.org>
Sorry about that, I'm beginning in sending patch for the kernel. I tried
to use the git send-email command, but I saw after that the command just
send email to the people I added, but not the mailing list. To be sure
to (re)send the last patch, I attached it to be sure to send it
"correctly", but not according to the recommended practice.
I will resend the whole patch list to the mailing list.
The patch you told was not intended to be self-consistant but a final
cleanup after the two patches I tried to send before. I splitted them
like that in order to keep them human readable as git tried to intrelace
the additions and removals, even if they were not related together.
Sorry again
Benjamin
On 03/08/2010 09:27 PM, Michael Poole wrote:
> Benjamin Tissoires writes:
>
>>>
>>> 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 ?
>>
>> Cheers,
>> Benjamin
>
> The recommended practice for sending patches is (from
> Documentation/SubmittingPatches) "7) No MIME, no links, no compression,
> no attachments. Just plain text."
>
> I'm a bit mystified, though -- if magicmouse_setup_input() is from "the
> old implementation", where is the new implementation? Jiri's
> hid/for-next and hid/master trees definitely use the input device that
> it sets up. The "magicmouse_input_mapping" function that shows up at
> the end of your patch doesn't exist in those trees. The reason I didn't
> use input_mapping() initially was because it only allows setting up one
> input field, and the touch records generate multiple types of events.
>
> Michael Poole
next prev parent reply other threads:[~2010-03-08 20:51 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 [this message]
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
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=4B956358.80608@tls.cena.fr \
--to=tissoire@tls.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 \
--cc=tissoire@cena.fr \
/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.