From: Benson Leung <bleung@google.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Guenter Roeck <groeck@chromium.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
bleung@chromium.org
Subject: Re: [PATCH] HID: i2c-hid: allocate hid buffers for real worst case
Date: Wed, 13 Sep 2017 08:00:36 -0700 [thread overview]
Message-ID: <20170913150036.GA66089@decatoncale.mtv.corp.google.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1709130751380.4703@jbgna.fhfr.qr>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hi Jiri,
On Wed, Sep 13, 2017 at 07:52:20AM -0700, Jiri Kosina wrote:
> > Oops, I must have cut it off on accident while removing ChromeOS
> > specific tags, the original commit is here:
> >
> > https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/475212
>
> Ok, thanks, will use that one. How about
>
> Reviewed-by: Benson Leung <bleung@chromium.org>
>
> which is missing in the mail you've sent, but is there in the above
> reference commit?
Submission looks good to me. Go ahead and add.
Reviewed-by: Benson Leung <bleung@chromium.org>
Thanks,
Benson
--
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-09-13 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 17:55 [PATCH] HID: i2c-hid: allocate hid buffers for real worst case Dmitry Torokhov
2017-09-13 14:02 ` Jiri Kosina
2017-09-13 14:49 ` Dmitry Torokhov
2017-09-13 14:52 ` Jiri Kosina
2017-09-13 15:00 ` Benson Leung [this message]
2017-09-13 16:18 ` Jiri Kosina
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=20170913150036.GA66089@decatoncale.mtv.corp.google.com \
--to=bleung@google.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bleung@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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