linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Joseph, Jithu" <jithu.joseph@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Hans de Goede <hdegoede@redhat.com>,
	Mark Gross <markgross@kernel.org>
Cc: Kuppuswamy Sathyanarayanan
	<sathyanarayanan.kuppuswamy@linux.intel.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 drivers-x86 tree
Date: Fri, 23 Aug 2024 12:16:50 -0700	[thread overview]
Message-ID: <98e7c093-4b1f-409d-97da-65bfc9c4bf1c@intel.com> (raw)
In-Reply-To: <20240820134354.2aec355d@canb.auug.org.au>



On 8/19/2024 8:43 PM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the drivers-x86 tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/arch/x86/ifs:2: /home/sfr/next/next/drivers/platform/x86/intel/ifs/ifs.h:131: WARNING: Title underline too short.
> 
> Structural Based Functional Test at Field (SBAF):
> ------------------------------------------------
> 
> Introduced by commit
> 
>   0a3e4e94d137 ("platform/x86/intel/ifs: Add SBAF test image loading support")
> 

Hi Stephen,

Thanks for reporting this. Below fix has been sent by Sathya to Hans (and the list)

https://lore.kernel.org/lkml/20240823184337.2923179-1-sathyanarayanan.kuppuswamy@linux.intel.com/

Thanks
Jithu




  parent reply	other threads:[~2024-08-23 19:20 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  3:43 linux-next: build warning after merge of the drivers-x86 tree Stephen Rothwell
2024-08-20  4:31 ` Kuppuswamy Sathyanarayanan
2024-08-23 19:16 ` Joseph, Jithu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-30 10:45 Stephen Rothwell
2025-04-30 10:51 ` Antheas Kapenekakis
2025-04-30 10:55   ` Ilpo Järvinen
2025-04-30 11:01     ` Antheas Kapenekakis
2025-04-30 11:07       ` Ilpo Järvinen
2024-07-15  7:03 Stephen Rothwell
2024-01-05  6:29 Stephen Rothwell
2023-02-03  2:53 Stephen Rothwell
2023-02-03  9:25 ` Hans de Goede
2021-02-04  5:13 Stephen Rothwell
2021-02-04  7:38 ` Hans de Goede
2021-02-04 15:05   ` Andy Shevchenko
2020-02-10 23:35 Stephen Rothwell
2020-02-10 23:39 ` Kammela, Gayatri
2020-02-11 21:07 ` Andy Shevchenko
2020-01-10  3:57 Stephen Rothwell
2020-01-10  9:47 ` Andy Shevchenko
2017-06-30  4:00 Stephen Rothwell
2017-06-30  5:12 ` Arvind Yadav
2017-07-01  3:32 ` Darren Hart
2017-05-19  3:23 Stephen Rothwell
2017-05-19 22:09 ` Darren Hart
2017-05-22 18:03   ` Andy Shevchenko
2017-05-25 23:34     ` Stephen Rothwell
2017-05-26  8:25       ` Arnd Bergmann
2017-05-26  8:35         ` Stephen Rothwell
2017-05-26  9:04           ` Andy Shevchenko
2017-05-26  9:07             ` Stephen Rothwell
2017-05-26  9:52               ` Andy Shevchenko
2016-12-14  2:50 Stephen Rothwell
2016-12-14 22:21 ` Darren Hart
2016-12-14 22:59   ` Darren Hart
2016-12-15  0:02     ` Stephen Rothwell
2016-12-15  4:07       ` Darren Hart
2010-08-27  1:59 Stephen Rothwell
2010-08-27  2:51 ` Matthew Garrett
2010-08-27  7:40   ` Dmitry Torokhov
2010-08-30  2:51     ` Stephen Rothwell
2010-06-25  3:25 Stephen Rothwell
2010-06-25  3:31 ` Matthew Garrett
2010-06-25  3:41 ` Matthew Garrett
2010-06-25  4:16   ` Stephen Rothwell

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=98e7c093-4b1f-409d-97da-65bfc9c4bf1c@intel.com \
    --to=jithu.joseph@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --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).