From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 1/1] Documentation: core-api: Drop :export: for int_log.h
Date: Tue, 25 Jul 2023 17:06:30 +0300 [thread overview]
Message-ID: <ZL/W5rc043oPLfMV@smile.fi.intel.com> (raw)
In-Reply-To: <b761d010-ef21-4be6-b6c3-678498b7fa71@sirena.org.uk>
On Tue, Jul 25, 2023 at 02:46:33PM +0100, Mark Brown wrote:
> On Tue, Jul 25, 2023 at 07:12:25AM -0600, Jonathan Corbet wrote:
> > Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
>
> > > The :export: keyword makes sense only for C-files, where EXPORT_SYMBOL()
> > > might appear. Otherwise kernel-doc may not produce anything out of this
> > > file.
>
> > So I still can't take this patch for the reasons described before. It
> > looks like Mark took the patch that added the problem, so perhaps he
> > should be a recipient of this one too? I'll add him to the CC...
>
> Is this the same patch I applied yesterday or a different one?
Hmm...
I do not see anything like this patch in your current ASoC for-next
(nor in for-6.6). Did I look into wrong branch?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-07-25 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:49 [PATCH v2 1/1] Documentation: core-api: Drop :export: for int_log.h Andy Shevchenko
2023-07-25 13:12 ` Jonathan Corbet
2023-07-25 13:16 ` Andy Shevchenko
2023-07-25 13:46 ` Mark Brown
2023-07-25 14:06 ` Andy Shevchenko [this message]
2023-07-25 14:27 ` Mark Brown
2023-07-25 14:40 ` Andy Shevchenko
2023-07-25 14:51 ` Mark Brown
2023-07-25 15:16 ` Andy Shevchenko
2023-07-25 19:20 ` Mark Brown
2023-07-26 14:45 ` 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=ZL/W5rc043oPLfMV@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).