mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Manuel Ebner <manuelebner@mailbox.org>,
	David Lechner <dlechner@baylibre.com>,
	Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH] Documentation: ABI: fix brackets and bracelets
Date: Thu, 11 Jun 2026 21:46:45 +0300	[thread overview]
Message-ID: <aisClWbXCX-XjVJ1@ashevche-desk.local> (raw)
In-Reply-To: <20260611171520.0a96ac83@jic23-huawei>

On Thu, Jun 11, 2026 at 05:15:20PM +0100, Jonathan Cameron wrote:
> On Thu, 11 Jun 2026 13:54:04 +0200
> Manuel Ebner <manuelebner@mailbox.org> wrote:
> > On Thu, 2026-06-11 at 10:46 +0100, Jonathan Cameron wrote:
> > > On Thu, 11 Jun 2026 10:56:21 +0200
> > > Manuel Ebner <manuelebner@mailbox.org> wrote:

...

> > > Take a look at hos this stuff is routed into upstream.  Each 
> > > subsystem 'owns' their own documentation.  So this needs splitting up
> > > on a per subsystem basis.  I'll also note that you've only +CC IIO folk
> > > so you aren't going to get much review on the rest!  
> > 
> > I send it to the addresses get_maintainer returned, except the git blame
> > ones. How can I find out who to send this to?
> 
> Some are easier to track down than others - look up related subsystems
> in maintainers + look at anyone who has made significant changes to the files
> in question.  However, some folk who work on Docs don't necessarily hang
> around so also useful to use lore.kernel.org to see if they have been
> on the list recently.  Also sometimes it is a bit fiddlier so look
> at the original commits - that lets you find out what the files are associated
> with.

Also Cc Randy Dunlap, he is interested in documentation fixes.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-06-11 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  8:56 Manuel Ebner
2026-06-11  9:46 ` Jonathan Cameron
2026-06-11 11:54   ` Manuel Ebner
2026-06-11 16:15     ` Jonathan Cameron
2026-06-11 18:46       ` Andy Shevchenko [this message]
2026-06-11 18:44 ` 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=aisClWbXCX-XjVJ1@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuelebner@mailbox.org \
    --cc=nuno.sa@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®