From: "Ahmed S. Darwish" <a.darwish@linutronix.de>
To: ycollette.nospam@free.fr
Cc: Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Wagner <wagi@monom.org>, Tom Zanussi <zanussi@kernel.org>,
"Srivatsa S. Bhat" <srivatsa@csail.mit.edu>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 5.10.30-rt37
Date: Tue, 20 Apr 2021 13:03:21 +0200 [thread overview]
Message-ID: <YH60+fd0phU3oTL3@lx-t490> (raw)
In-Reply-To: <941471789.41891679.1618904363608.JavaMail.root@zimbra35-e6.priv.proxad.net>
On Tue, Apr 20, 2021, ycollette.nospam@free.fr wrote:
>
> net/xfrm/xfrm_state.c: In function 'xfrm_state_init':
> ./include/linux/seqlock.h:178:36: error: initialization of 'seqcount_spinlock_t *' {aka 'struct seqcount_spinlock *'} from incompatible pointer type 'seqcount_t *' {aka 'struct seqcount *'} [-Werror=incompatible-pointer-types]
> 178 | seqcount_##lockname##_t *____s = (s); \
> | ^
...
> net/xfrm/xfrm_state.c:2666:2: note: in expansion of macro 'seqcount_spinlock_init'
> 2666 | seqcount_spinlock_init(&net->xfrm.xfrm_state_hash_generation,
> | ^~~~~~~~~~~~~~~~~~~~~~
There is a rebase error at:
247560698349 ("Merge tag 'v5.10.30' into v5.10-rt")
Cherry-pick mainline's commit:
bc8e0adff343 ("net: xfrm: Use sequence counter with associated spinlock")
and your compilation issue will be fixed.
Good luck,
--
Ahmed S. Darwish
next prev parent reply other threads:[~2021-04-20 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 22:47 [ANNOUNCE] 5.10.30-rt37 Steven Rostedt
2021-04-20 7:39 ` ycollette.nospam
2021-04-20 11:03 ` Ahmed S. Darwish [this message]
2021-05-03 20:39 ` Bajjuri, Praneeth
2021-05-07 20:03 ` Steven Rostedt
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=YH60+fd0phU3oTL3@lx-t490 \
--to=a.darwish@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=ycollette.nospam@free.fr \
--cc=zanussi@kernel.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 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).