From: Thomas Gleixner <tglx@linutronix.de>
To: Clark Williams <williams@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.6.11-rt26
Date: Mon, 4 Feb 2013 18:16:03 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1302041812460.11905@ionos> (raw)
In-Reply-To: <20130204105900.63bd5fae@riff.lan>
On Mon, 4 Feb 2013, Clark Williams wrote:
> More changes; I was running into a collision with the name kmap_prot.
Bah. I knew that I should have decided that today is still part of the
weekend.
Pushed out rt27 with the fixed merged back. Sorry for the noise.
Thanks,
tglx
next prev parent reply other threads:[~2013-02-04 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 14:58 [ANNOUNCE] 3.6.11-rt26 Thomas Gleixner
2013-02-04 15:02 ` Thomas Gleixner
2013-02-04 15:54 ` Clark Williams
2013-02-04 16:59 ` Clark Williams
2013-02-04 17:16 ` Thomas Gleixner [this message]
2013-02-05 7:31 ` Qiang Huang
2013-02-05 10:18 ` Thomas Gleixner
2013-02-07 17:11 ` [ANNOUNCE] 3.6.11-rt26 - interrupts again Tim Sander
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=alpine.LFD.2.02.1302041812460.11905@ionos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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