From: Steven Rostedt <rostedt@goodmis.org>
To: Carsten Emde <C.Emde@osadl.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.6.11.1-rt32
Date: Thu, 11 Apr 2013 13:50:45 -0400 [thread overview]
Message-ID: <1365702645.9609.41.camel@gandalf.local.home> (raw)
In-Reply-To: <515A364B.7070100@osadl.org>
On Tue, 2013-04-02 at 03:37 +0200, Carsten Emde wrote:
> Steven,
>
> > I'm pleased to announce the 3.6.11.1-rt32 stable release.
> Thank you.
>
> Your patch-3.6.11.1 additionally needs
> 23d3b8bfb8eb20e7d96afa09991e6a5ed1c83164 (net: qdisc busylock needs
> lockdep annotations) to avoid the compile error
> drivers/net/ppp/ppp_generic.c: In function ‘ppp_dev_init’:
> drivers/net/ppp/ppp_generic.c:1027:5: error: ‘struct net_device’ has no
> member named ‘qdisc_tx_busylock’
Hmm, I was able to do a full 3.6.11.1 allmodconfig without this (see
below). But I'll add it anyway.
>
> And since you apparently decided to backport
> 303c07db487be59ae9fda10600ea65ca11c21497 (ppp: set qdisc_tx_busylock to
> avoid LOCKDEP splat), you probably should also backport the related
Oh, I added this by mistake, and I believe this is what caused the above
compile problem. I reverted this as the first patch for .2, and I
compiled 3.6.11.1 with this revert on an allmodconfig.
-- Steve
> changes in bonding and team:
> - 49ee49202b4ac4be95d05e4bf24a9ac8b54c5528 (bonding: set
> qdisc_tx_busylock to avoid LOCKDEP splat)
> - b3c581d5d7130fc7f2eab9ab14c8de8882b42380 (team: set qdisc_tx_busylock
> to avoid LOCKDEP splat)
>
> -Carsten.
next prev parent reply other threads:[~2013-04-11 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 3:25 [ANNOUNCE] 3.6.11.1-rt32 Steven Rostedt
2013-04-02 1:37 ` Carsten Emde
2013-04-11 17:50 ` Steven Rostedt [this message]
2013-04-02 3:13 ` Carsten Emde
2013-04-09 17:46 ` Steven Rostedt
2013-04-14 21:13 ` Carsten Emde
2013-04-12 15:47 ` John Kacur
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=1365702645.9609.41.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).