linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] reset: Remove copy'n'paste redundancy in the comments
Date: Mon, 02 Sep 2019 16:04:23 +0200	[thread overview]
Message-ID: <1567433063.3666.7.camel@pengutronix.de> (raw)
In-Reply-To: <20190902131920.GK2680@smile.fi.intel.com>

Hi Andy,

On Mon, 2019-09-02 at 16:19 +0300, Andy Shevchenko wrote:
> On Mon, Aug 19, 2019 at 01:52:52PM +0300, Andy Shevchenko wrote:
> > It seems the commit bb475230b8e5
> > ("reset: make optional functions really optional")
> > brought couple of redundant lines in the comments.
> > 
> > Drop them here.
> 
> Any comment on this?

No, this looks correct to me. Thank for the patch!
Applied to reset/next.

regards
Philipp

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 10:52 [PATCH v1] reset: Remove copy'n'paste redundancy in the comments Andy Shevchenko
2019-09-02 13:19 ` Andy Shevchenko
2019-09-02 14:04   ` Philipp Zabel [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=1567433063.3666.7.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --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).