All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vegard Nossum <vegard.nossum@oracle.com>,
	Kent Gibson <warthog618@gmail.com>,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <siyanteng@loongson.cn>
Subject: Re: [PATCH v1 1/1] gpio: Remove legacy API documentation
Date: Thu, 16 May 2024 16:54:38 +0300	[thread overview]
Message-ID: <ZkYQHnF76WLIf8-r@smile.fi.intel.com> (raw)
In-Reply-To: <20240508101703.830066-1-andriy.shevchenko@linux.intel.com>

On Wed, May 08, 2024 at 01:17:01PM +0300, Andy Shevchenko wrote:
> In order to discourage people to use old and legacy GPIO APIs
> remove the respective documentation completely. It also helps
> further cleanups of the legacy GPIO API leftovers, which is
> ongoing task.

Bart, Linus, Kent, what do you think about this?

If there is a positive consensus, I would even dare to go for v6.10-rc2
with it.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2024-05-16 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 10:17 [PATCH v1 1/1] gpio: Remove legacy API documentation Andy Shevchenko
2024-05-08 10:20 ` Andy Shevchenko
2024-05-16 13:54 ` Andy Shevchenko [this message]
2024-05-16 15:19   ` Kent Gibson
2024-05-17  9:47   ` Bartosz Golaszewski
2024-05-17 10:01     ` Linus Walleij
2024-05-21 10:12 ` Hu Haowen
2024-05-27 14:50 ` Bartosz Golaszewski

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=ZkYQHnF76WLIf8-r@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=alexs@kernel.org \
    --cc=brgl@bgdev.pl \
    --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=siyanteng@loongson.cn \
    --cc=vegard.nossum@oracle.com \
    --cc=warthog618@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.