public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: David Laight <David.Laight@ACULAB.COM>,
	'Dave Penkler' <dpenkler@gmail.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] staging: gpib: Fix i386 build issue
Date: Fri, 6 Dec 2024 11:17:07 -0800	[thread overview]
Message-ID: <b94d3f72-7a4d-44a5-baeb-5febac6b64e6@roeck-us.net> (raw)
In-Reply-To: <ba3bf2c6c59f4019a3d502cb0b703d7b@AcuMS.aculab.com>

Hi David,

On 12/6/24 10:02, David Laight wrote:
> From: Dave Penkler
>> Sent: 04 December 2024 16:21
>>
>> These drivers cast resource_type_t to void * causing the build to fail.
>>
>> With CONFIG_X86_PAE enabled the resource_size_t type is a 64bit unsigned
>> int which cannot be cast to a 32 bit pointer.
>>
>> Disable these drivers if X68_PAE is enabled
> 
> You missed the obvious typo :-)
> 

FWIW, I fail to see that typo as well, so I am not sure if it is really
that obvious.

> There is also a proposal to just remove PAE support.
> Mostly because it is likely to have bit-rotted and isn't really
> needed now 64bit code is common.
> 

Presumably that removal would not be 6.13 material, though, and I hope
that there _some_ fix will make it into 6.13.

Thanks,
Guenter


  reply	other threads:[~2024-12-06 19:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 16:21 [PATCH v5] staging: gpib: Fix i386 build issue Dave Penkler
2024-12-06 18:02 ` David Laight
2024-12-06 19:17   ` Guenter Roeck [this message]
2024-12-09 16:01 ` Geert Uytterhoeven
2024-12-09 16:12   ` Dave Penkler
2024-12-09 16:18   ` Guenter Roeck
2024-12-09 16:27     ` Geert Uytterhoeven
2024-12-09 16:35       ` Guenter Roeck
2024-12-10  7:52     ` Geert Uytterhoeven
2024-12-10  8:39       ` Greg KH
2024-12-10  9:02         ` Geert Uytterhoeven
2024-12-11  0:56           ` Guenter Roeck

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=b94d3f72-7a4d-44a5-baeb-5febac6b64e6@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=David.Laight@ACULAB.COM \
    --cc=dpenkler@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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