All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Shiju Jose <shiju.jose@huawei.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the edac tree
Date: Fri, 28 Feb 2025 07:44:30 -0700	[thread overview]
Message-ID: <87jz9ann75.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250228103559.GAZ8GRj0xj6AKGVLj3@fat_crate.local>

Borislav Petkov <bp@alien8.de> writes:

> This branch is now public and immutable so you need to send real patches with
> commit messages which fix things ontop. But before you do...
>
>> diff --git a/Documentation/subsystem-apis.rst b/Documentation/subsystem-apis.rst
>> index b52ad5b969d4..ff4fe8c936c8 100644
>> --- a/Documentation/subsystem-apis.rst
>> +++ b/Documentation/subsystem-apis.rst
>> @@ -71,6 +71,7 @@ Other subsystems
>>  
>>     accounting/index
>>     cpu-freq/index
>> +   edac/index
>>     fpga/index
>>     i2c/index
>>     iio/index 
>> >
>> >--
>
> ... let's see what Jon says.
>
> Jon, ack?
>
> Is that the right place to put this in?

That will solve the problem for now, though that file is kind of a
dumping ground.  I'll clearly have to get back to my project of better
organizing the device docs...

Thanks,

jon

  reply	other threads:[~2025-02-28 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28  7:51 linux-next: build warning after merge of the edac tree Stephen Rothwell
2025-02-28 10:04 ` Shiju Jose
2025-02-28 10:35   ` Borislav Petkov
2025-02-28 14:44     ` Jonathan Corbet [this message]
2025-02-28 15:05       ` Borislav Petkov
2025-04-01  4:39 ` Stephen Rothwell
2025-04-01 10:44   ` Borislav Petkov
2025-04-01 12:02     ` Shiju Jose

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=87jz9ann75.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=bp@alien8.de \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shiju.jose@huawei.com \
    --cc=tony.luck@intel.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.