From: Nick Crews <ncrews@chromium.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Benson Leung <bleung@chromium.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Duncan Laurie <dlaurie@chromium.org>
Subject: Re: [PATCH -next] platform/chrome: Fix off-by-one error in wilco_ec/debugfs.c
Date: Thu, 21 Feb 2019 12:09:06 -0700 [thread overview]
Message-ID: <CAHX4x851YhO8CmzMheM6bOv2+Y0jX8ZVY011CuuvO0qH-FPAGQ@mail.gmail.com> (raw)
In-Reply-To: <20190221070704.GD1711@kadam>
Thanks Dan, noted.
On Thu, Feb 21, 2019 at 11:31 AM Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> On Wed, Feb 20, 2019 at 03:15:18PM -0700, Nick Crews wrote:
> > Fixing something after it's already in the tree was a new
> > process for me, so I tried to copy other people's examples. Please
> > let me know if there's anything else I should do something different
> > next time.
>
> I seldom mention how much I like Reported-by tags because it makes me
> seem needy... Also in this case it doesn't matter because it's going to
> get folded into the original patch so it's going to be lost anyway. But
> since you're asking process questions, the Reported-by cookie is nice.
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2019-02-21 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 21:58 [PATCH -next] platform/chrome: Fix off-by-one error in wilco_ec/debugfs.c Nick Crews
2019-02-20 22:06 ` Enric Balletbo i Serra
2019-02-20 22:15 ` Nick Crews
2019-02-21 7:58 ` Enric Balletbo i Serra
2019-02-21 18:31 ` Dan Carpenter
2019-02-21 19:09 ` Nick Crews [this message]
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=CAHX4x851YhO8CmzMheM6bOv2+Y0jX8ZVY011CuuvO0qH-FPAGQ@mail.gmail.com \
--to=ncrews@chromium.org \
--cc=bleung@chromium.org \
--cc=dan.carpenter@oracle.com \
--cc=dlaurie@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=kernel-janitors@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;
as well as URLs for NNTP newsgroup(s).