On Tue, Feb 25, 2025 at 11:10:29AM +0200, Jani Nikula wrote:
> On Mon, 24 Feb 2025, Dan Carpenter wrote:
> > On Mon, Feb 24, 2025 at 03:14:33PM +0200, Jani Nikula wrote:
> >> On Wed, 19 Feb 2025, Dan Carpenter wrote:
> >> > The "id" variable is an enum and in this context it's treated as an
> >>
On Tue, 25 Feb 2025 10:10:29 +0100,
Jani Nikula wrote:
>
> On Mon, 24 Feb 2025, Dan Carpenter wrote:
> > On Mon, Feb 24, 2025 at 03:14:33PM +0200, Jani Nikula wrote:
> >> On Wed, 19 Feb 2025, Dan Carpenter wrote:
> >> > The "id" variable is an enum and in this context it's treated as an
> >> > u
On Mon, 24 Feb 2025, Dan Carpenter wrote:
> On Mon, Feb 24, 2025 at 03:14:33PM +0200, Jani Nikula wrote:
>> On Wed, 19 Feb 2025, Dan Carpenter wrote:
>> > The "id" variable is an enum and in this context it's treated as an
>> > unsigned int so the error handling can never trigger. The
>> > ->get
On Mon, Feb 24, 2025 at 03:14:33PM +0200, Jani Nikula wrote:
> On Wed, 19 Feb 2025, Dan Carpenter wrote:
> > The "id" variable is an enum and in this context it's treated as an
> > unsigned int so the error handling can never trigger. The
> > ->get_client_id() functions do not currently return an
On Wed, 19 Feb 2025, Dan Carpenter wrote:
> The "id" variable is an enum and in this context it's treated as an
> unsigned int so the error handling can never trigger. The
> ->get_client_id() functions do not currently return any errors but
> I imagine that if they did, then the intention was to
On Wed, 19 Feb 2025, Dan Carpenter wrote:
> On Wed, Feb 19, 2025 at 05:17:56PM +0200, Jani Nikula wrote:
>> On Wed, 19 Feb 2025, Dan Carpenter wrote:
>> > The "id" variable is an enum and in this context it's treated as an
>> > unsigned int so the error handling can never trigger.
>>
>> When wou
On Wed, Feb 19, 2025 at 05:17:56PM +0200, Jani Nikula wrote:
> On Wed, 19 Feb 2025, Dan Carpenter wrote:
> > The "id" variable is an enum and in this context it's treated as an
> > unsigned int so the error handling can never trigger.
>
> When would that be true with GCC?
The C standard give com
On Wed, 19 Feb 2025, Dan Carpenter wrote:
> The "id" variable is an enum and in this context it's treated as an
> unsigned int so the error handling can never trigger.
When would that be true with GCC?
BR,
Jani.
> The
> ->get_client_id() functions do not currently return any errors but
> I imag
The "id" variable is an enum and in this context it's treated as an
unsigned int so the error handling can never trigger. The
->get_client_id() functions do not currently return any errors but
I imagine that if they did, then the intention was to return
VGA_SWITCHEROO_UNKNOWN_ID on error. Let's c
