From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v2 1/2] pinctrl: Proofreading and updating the documentation accordingly
Date: Tue, 17 Jan 2023 17:00:20 +0200 [thread overview]
Message-ID: <Y8a4BAotZAax9Zx4@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdYTFDsU7xhu812Lh1mA1Hs9kGeid+akR84ervAsaxVYkg@mail.gmail.com>
On Tue, Jan 17, 2023 at 03:26:31PM +0100, Linus Walleij wrote:
> On Tue, Jan 17, 2023 at 3:24 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
> > Actually I have missed the repetition of the comment I put in v1,
> > i.e. that this would be good to be attached to my PR where the
> > struct pinfunction et al. have been introduced. Can I have your
> > Ack?
>
> Sure go ahead,
So, which tag to use?
"Acked-by: Linus Walleij <linus.walleij@linaro.org>" ?
> I can also take out the patches if you rather
> include them with a pull request.
It would be the best, thanks!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-01-17 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 15:33 [PATCH v2 1/2] pinctrl: Proofreading and updating the documentation accordingly Andy Shevchenko
2023-01-16 15:33 ` [PATCH v2 2/2] pinctrl: Proofreading and updating the documentation (part 2) Andy Shevchenko
2023-01-17 13:15 ` [PATCH v2 1/2] pinctrl: Proofreading and updating the documentation accordingly Linus Walleij
2023-01-17 14:24 ` Andy Shevchenko
2023-01-17 14:26 ` Linus Walleij
2023-01-17 15:00 ` Andy Shevchenko [this message]
2023-01-17 15:43 ` Andy Shevchenko
2023-01-17 15:44 ` Andy Shevchenko
2023-01-17 18:16 ` Linus Walleij
2023-01-17 18:28 ` Andy Shevchenko
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=Y8a4BAotZAax9Zx4@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@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).