public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Matthew Garrett <mjg59@srcf•ucam.org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Alan Cox <alan@linux•intel.com>,
	Greg Kroah-Hartman <gregkh@suse•de>
Subject: linux-next: build warning after merge of the drivers-x86 tree
Date: Fri, 25 Jun 2010 13:25:45 +1000	[thread overview]
Message-ID: <20100625132545.50e226e3.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 623 bytes --]

Hi Matthew,

After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/platform/x86/Kconfig:542:warning: type of 'RAR_REGISTER' redefined from 'tristate' to 'boolean'

Caused by commit b8fd1646cc932c911c4d836f7fd9624c05722a2d ("rar: Move the
RAR driver into the right place as its now clean").

RAR_REGISTER is also still defined in
drivers/staging/rar_register/Kconfig ...  Also, that commit did not move
intel_rar_register.c from staging ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2010-06-25  3:25 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25  3:25 Stephen Rothwell [this message]
2010-06-25  3:31 ` linux-next: build warning after merge of the drivers-x86 tree Matthew Garrett
2010-06-25  3:41 ` Matthew Garrett
2010-06-25  4:16   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
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
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
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
2017-06-30  4:00 Stephen Rothwell
2017-06-30  5:12 ` Arvind Yadav
2017-07-01  3:32 ` Darren Hart
2020-01-10  3:57 Stephen Rothwell
2020-01-10  9:47 ` Andy Shevchenko
2020-02-10 23:35 Stephen Rothwell
2020-02-10 23:39 ` Kammela, Gayatri
2020-02-11 21:07 ` Andy Shevchenko
2021-02-04  5:13 Stephen Rothwell
2021-02-04  7:38 ` Hans de Goede
2021-02-04 15:05   ` Andy Shevchenko
2023-02-03  2:53 Stephen Rothwell
2023-02-03  9:25 ` Hans de Goede
2024-01-05  6:29 Stephen Rothwell
2024-07-15  7:03 Stephen Rothwell
2024-08-20  3:43 Stephen Rothwell
2024-08-20  4:31 ` Kuppuswamy Sathyanarayanan
2024-08-23 19:16 ` Joseph, Jithu
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

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=20100625132545.50e226e3.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=alan@linux$(echo .)intel.com \
    --cc=gregkh@suse$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mjg59@srcf$(echo .)ucam.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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