linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Niyas Sait <niyas.sait@linaro.org>
Subject: Re: [PATCH v1 1/1] pinctrl: Proofreading and updating the documentation accordingly
Date: Thu, 12 Jan 2023 13:46:20 +0200	[thread overview]
Message-ID: <Y7/zDAhyuoJrMfiU@smile.fi.intel.com> (raw)
In-Reply-To: <Y70sHNqLVvx6UF41@debian.me>

On Tue, Jan 10, 2023 at 04:13:00PM +0700, Bagas Sanjaya wrote:
> On Mon, Jan 09, 2023 at 10:54:56PM +0200, Andy Shevchenko wrote:
> > diff --git a/Documentation/driver-api/pin-control.rst b/Documentation/driver-api/pin-control.rst
> > index 0022e930e93e..0274313e9997 100644
> > --- a/Documentation/driver-api/pin-control.rst
> > +++ b/Documentation/driver-api/pin-control.rst
> > @@ -11,7 +11,7 @@ This subsystem deals with:
> >  - Multiplexing of pins, pads, fingers (etc) see below for details
> >  
> >  - Configuration of pins, pads, fingers (etc), such as software-controlled
> > -  biasing and driving mode specific pins, such as pull-up/down, open drain,
> > +  biasing and driving mode specific pins, such as pull-up, pull-down, open drain,
> >    load capacitance etc.
> >  
> >  Top-level interface

Thank you for your input, can I add it as a separate change on top of mine? I would like to keep
my stuff separate from the more intrusive changes (scope is mostly on the examples and function
references). If yes, can you provide your SoB tag?

Btw, the pad table is not align on purpose AFAIU how BGA looks from the bottom.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-01-12 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 20:54 [PATCH v1 1/1] pinctrl: Proofreading and updating the documentation accordingly Andy Shevchenko
2023-01-10  8:19 ` kernel test robot
2023-01-10  9:13 ` Bagas Sanjaya
2023-01-12 11:46   ` Andy Shevchenko [this message]
2023-01-13  2:15     ` Bagas Sanjaya

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=Y7/zDAhyuoJrMfiU@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 \
    --cc=niyas.sait@linaro.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).