mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bajjuri, Praneeth" <praneeth@ti.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: 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>
Subject: Re: [ANNOUNCE] 5.10.30-rt37
Date: Mon, 3 May 2021 15:39:19 -0500	[thread overview]
Message-ID: <c3b8a530-2ade-5876-5c93-7f83286796b8@ti.com> (raw)
In-Reply-To: <20210419184731.246fa474@gandalf.local.home>



On 4/19/2021 5:47 PM, Steven Rostedt wrote:
> 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")

Thanks for this fix, Cherry-pick resolved rt stable integration issue 
that i was seeing.

Is this fix going to be posted for v5.10-rt too ?

> 
> and your compilation issue will be fixed.


  parent reply	other threads:[~2021-05-03 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 22:47 Steven Rostedt
2021-04-20  7:39 ` ycollette.nospam
2021-04-20 11:03   ` Ahmed S. Darwish
2021-05-03 20:39 ` Bajjuri, Praneeth [this message]
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=c3b8a530-2ade-5876-5c93-7f83286796b8@ti.com \
    --to=praneeth@ti.com \
    --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=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
all inboxes | Powered by JetHome®