From: Chase Douglas <chase.douglas@canonical.com>
To: Jeffrey Brown <jeffbrown@android.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
Henrik Rydberg <rydberg@euromail.se>,
Simon Budig <simon@budig.de>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] hid-magicmouse: Increase evdev buffer size
Date: Mon, 04 Apr 2011 14:55:03 -0400 [thread overview]
Message-ID: <4D9A1407.6030308@canonical.com> (raw)
In-Reply-To: <BANLkTikG-ku9mDebcaPKTwv3X0N+OKiyYQ@mail.gmail.com>
On 04/04/2011 02:13 PM, Jeffrey Brown wrote:
> On Mon, Apr 4, 2011 at 5:43 AM, Jiri Kosina <jkosina@suse.cz> wrote:
>> I'd happuly take Chase's patch, but want to make sure that we don't cause
>> any changes that would make backwards compatilibity an issue later.
>
> There should be no compatibility issues. However, we might be better
> off in the long term taking (some variation of) these patches instead.
I like the proposed changes, but I want to ensure stable kernel releases
aren't left out of the fix for hid-magicmouse. I don't know the best way
forward, but here's one possibility:
1. Apply my patch to manually set the buffer size hint
2. It gets sent to stable trees due to the 'Cc: stable@kernel.org' line
3. Apply Jeffrey's patches, including a reversion of my buffer size hint
Obviously the extra application and reversion is odd, but this seems the
easiest way forward given that the patches already exist and can be
applied without issue.
Thanks,
-- Chase
next prev parent reply other threads:[~2011-04-04 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 21:03 [PATCH resend] hid-magicmouse: Increase evdev buffer size Chase Douglas
2011-04-01 23:51 ` Jeffrey Brown
2011-04-02 16:36 ` Chase Douglas
2011-04-04 12:20 ` Simon Budig
2011-04-04 12:43 ` Jiri Kosina
2011-04-04 18:13 ` Jeffrey Brown
2011-04-04 18:55 ` Chase Douglas [this message]
2011-04-04 21:39 ` Dmitry Torokhov
2011-04-04 21:46 ` Chase Douglas
2011-04-05 19:45 ` Chase Douglas
2011-04-06 13:18 ` Jiri Kosina
2011-04-04 11:50 ` Henrik Rydberg
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=4D9A1407.6030308@canonical.com \
--to=chase.douglas@canonical.com \
--cc=jeffbrown@android.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
--cc=simon@budig.de \
/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