linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Flavio Suligoi <f.suligoi@asem.it>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v4] Documentation: ACPI: explain how to use gpio-line-names
Date: Thu, 12 Nov 2020 13:50:05 +0000	[thread overview]
Message-ID: <0ffeff9c510c40198ea0384a6d34323b@asem.it> (raw)
In-Reply-To: <20201112134042.GB4077@smile.fi.intel.com>

HI Andy,

> On Thu, Nov 12, 2020 at 02:15:45PM +0100, Flavio Suligoi wrote:
> > The "gpio-line-names" declaration is not fully
> > documented, so can be useful to add some important
> > information and one more example.
> >
> > This commit also fixes a trivial spelling mistake.
> 
> For the future contributions:
> 
> No need to resend each time you got a tag. Maintainers usually take them
> all at
> once when applying (esp. taking into account plenty of scripts which help
> to do
> this automatically).

ok

> 
> Also, no need to resend so often. Give a chance to others to review
> (minimum
> resend time is 24h)

ok, right!

> 
> --
> With Best Regards,
> Andy Shevchenko
> 

Regards,
Flavio

  reply	other threads:[~2020-11-12 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 13:15 [PATCH v4] Documentation: ACPI: explain how to use gpio-line-names Flavio Suligoi
2020-11-12 13:40 ` Andy Shevchenko
2020-11-12 13:50   ` Flavio Suligoi [this message]
2020-11-16 18:37 ` Rafael J. Wysocki

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=0ffeff9c510c40198ea0384a6d34323b@asem.it \
    --to=f.suligoi@asem.it \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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).