From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wl@xen.org>,
Juergen Gross <jgross@suse.com>,
George Dunlap <george.dunlap@citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: Backport request (was: [PATCH v2] tools: convert bitfields to unsigned type)
Date: Tue, 4 Jul 2023 17:42:33 +0200 [thread overview]
Message-ID: <4d049335-71fd-8fe0-0f9a-dfdd16fcf41e@suse.com> (raw)
In-Reply-To: <ZJwBkHLwKJNuhekG@MacBook-Air-de-Roger.local>
On 28.06.2023 11:46, Roger Pau Monné wrote:
> On Mon, May 08, 2023 at 04:46:18PM +0000, Olaf Hering wrote:
>> clang complains about the signed type:
>>
>> implicit truncation from 'int' to a one-bit wide bit-field changes value from 1 to -1 [-Wsingle-bit-bitfield-constant-conversion]
>>
>> The potential ABI change in libxenvchan is covered by the Xen version based SONAME.
>>
>> Signed-off-by: Olaf Hering <olaf@aepfle.de>
>
> Can we have this one backported to 4.17 at least?
Hmm, while perhaps simple enough, in principle this wouldn't be a backporting
candidate. May I ask why you consider this relevant? Plus is the mentioned
"potential ABI change" safe to take on a stable branch? There's not going to
be any SONAME change ...
Jan
next prev parent reply other threads:[~2023-07-04 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:46 [PATCH v2] tools: convert bitfields to unsigned type Olaf Hering
2023-05-09 7:10 ` Juergen Gross
2023-05-10 17:00 ` Anthony PERARD
2023-06-28 9:46 ` Backport request (was: [PATCH v2] tools: convert bitfields to unsigned type) Roger Pau Monné
2023-07-04 15:42 ` Jan Beulich [this message]
2023-07-04 15:55 ` Roger Pau Monné
2023-07-04 16:04 ` Jan Beulich
2023-07-04 16:10 ` Roger Pau Monné
2023-07-04 16:16 ` Jan Beulich
2023-07-06 8:53 ` Jan Beulich
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=4d049335-71fd-8fe0-0f9a-dfdd16fcf41e@suse.com \
--to=jbeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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.