From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
Date: Sat, 14 Mar 2009 00:04:40 -0700 [thread overview]
Message-ID: <49BB5708.1090604@goop.org> (raw)
Change fef20d9c1380f04ba9492d6463148db07b413708, "vsprintf: unify the
format decoding layer for its 3 users", causes a regression in xenbus
which results in no devices getting attached to a new domain. Reverting
fef20d9c1380f04ba9492d6463148db07b413708 and
39e874f8afbdb3745e2406ce4ecbde9ac4cbaa78 fixes the problem.
I haven't identified what format string is being handled wrongly, so I
don't know what the precise bug is. The most complex looking format in
use seems to be %.*s; there's also "%s/%s", "%i" and "%lX".
J
next reply other threads:[~2009-03-14 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 7:04 Jeremy Fitzhardinge [this message]
2009-03-14 11:08 ` Vegard Nossum
2009-03-14 16:11 ` Jeremy Fitzhardinge
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=49BB5708.1090604@goop.org \
--to=jeremy@goop.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®