All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input <linux-input@vger.kernel.org>,
	Henrik Rydberg <rydberg@euromail.se>
Subject: Re: [PATCH 11/14] HID: multitouch: validate feature report details
Date: Wed, 4 Sep 2013 11:57:24 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1309041155460.3684@pobox.suse.cz> (raw)
In-Reply-To: <CAN+gG=Fx5bjcPndRSBBJTvZFC2GOegigkzL3De8iK7vauiPq1g@mail.gmail.com>

On Mon, 2 Sep 2013, Benjamin Tissoires wrote:

> > Given the 12 flaws, what do you see as the best way forward?
> 
> If Jiri thinks we can wait one more week for some of these patches (I
> know that the most critical one, 1/14 is already on its way to Linus),
> then I can handle the v2, but not before Friday. Again, I think the
> current patch series is perfectly fine for distributions as they can
> add/remove things more easily than we can do in master.

I agree.

1/14 will go to Linus shortly. The rest is public, and distributions are 
taking it depending on their requirements, but I'd like to have the 
patchset polished before pushing it to Linus.

Therefore putting the rest on hold now, and waiting for v2.

Thanks a lot to both of you,

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2013-09-04  9:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 20:31 [PATCH 11/14] HID: multitouch: validate feature report details Jiri Kosina
2013-08-29  8:59 ` Benjamin Tissoires
2013-08-29 19:41   ` Kees Cook
2013-08-30 15:27     ` Benjamin Tissoires
2013-08-30 18:27       ` Kees Cook
2013-09-02 12:56         ` Benjamin Tissoires
2013-09-04  9:57           ` Jiri Kosina [this message]
2013-09-04 14:59             ` Josh Boyer
2013-09-04 15:41               ` Josh Boyer
2013-09-04 16:31         ` Kees Cook
2013-09-09 13:50           ` 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=alpine.LNX.2.00.1309041155460.3684@pobox.suse.cz \
    --to=jkosina@suse.cz \
    --cc=benjamin.tissoires@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-input@vger.kernel.org \
    --cc=rydberg@euromail.se \
    /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.