mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Nick Crews <ncrews@chromium.org>, bleung@chromium.org
Cc: linux-kernel@vger.kernel.org, dlaurie@chromium.org,
	derat@google.com, groeck@google.com, dtor@google.com,
	sjg@chromium.org, alevkoy@chromium.org, keithshort@chromium.org
Subject: Re: [PATCH v4 1/2] platform/chrome: wilco_ec: Fix documentation for debugfs raw attribute
Date: Mon, 15 Apr 2019 16:02:18 +0200	[thread overview]
Message-ID: <5ddf74d5-5536-68bc-d8ee-e0c92f7dcb72@collabora.com> (raw)
In-Reply-To: <20190412181443.239166-1-ncrews@chromium.org>

Hi Nick,

On 12/4/19 20:14, Nick Crews wrote:
> In a previous refactor [repo chrome-platform, branch for-next,
> commit 9cced499d6fdb60434ffa94f8f4b5087ad35802b
> ("platform/chrome: wilco_ec: Standardize mailbox interface")], the
> documentation for the raw debugfs attribute became incorrect, but I
> forgot to fix it. This patch fixes it, as well as de-duplicates
> the documentation by removing it from the source file header comment.
> 
> Signed-off-by: Nick Crews <ncrews@chromium.org>
> ---
>  Documentation/ABI/testing/debugfs-wilco-ec | 32 ++++++++++++++--------
>  drivers/platform/chrome/wilco_ec/debugfs.c | 27 +-----------------
>  2 files changed, 22 insertions(+), 37 deletions(-)

I'm going to squash this commit and queue for 5.2.

Thanks,
 Enric


      parent reply	other threads:[~2019-04-15 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 18:14 Nick Crews
2019-04-12 18:14 ` [PATCH v4 2/2] platform/chrome: wilco_ec: Add h1_gpio status to debugfs Nick Crews
2019-04-15 14:04   ` Enric Balletbo i Serra
2019-04-15 14:02 ` Enric Balletbo i Serra [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=5ddf74d5-5536-68bc-d8ee-e0c92f7dcb72@collabora.com \
    --to=enric.balletbo@collabora.com \
    --cc=alevkoy@chromium.org \
    --cc=bleung@chromium.org \
    --cc=derat@google.com \
    --cc=dlaurie@chromium.org \
    --cc=dtor@google.com \
    --cc=groeck@google.com \
    --cc=keithshort@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncrews@chromium.org \
    --cc=sjg@chromium.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
all inboxes | Powered by JetHome®