From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Mattia Dongili <malattia@linux.it>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86 <platform-driver-x86@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the drivers-x86 tree
Date: Tue, 22 Feb 2011 14:34:34 +0000 [thread overview]
Message-ID: <20110222143434.GA9720@srcf.ucam.org> (raw)
In-Reply-To: <20110222114601.GA936@kamineko.org>
On Tue, Feb 22, 2011 at 08:46:01PM +0900, Mattia Dongili wrote:
> how does linux-next work? should this patch be a separate commit or can
> it be folded into the offending one?
I'll fold it into the offending one and repush. Sorry about the
breakage, Stephen - I don't have DEBUG_ALLOC enabled so didn't see the
failure. Do you build with a defined configuration I can test against?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-02-22 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110222162206.c3fb0636.sfr@canb.auug.org.au>
[not found] ` <a8c6f32c-ccb5-4f65-b537-8bd1c11f7336@email.android.com>
2011-02-22 11:46 ` linux-next: build failure after merge of the drivers-x86 tree Mattia Dongili
2011-02-22 14:34 ` Matthew Garrett [this message]
2011-02-22 22:22 ` Stephen Rothwell
2021-07-28 16:48 Mark Brown
2021-07-28 17:01 ` Andy Shevchenko
2021-07-28 17:27 ` Kammela, Gayatri
2021-07-28 17:55 ` Hans de Goede
2021-07-28 17:59 ` Kammela, Gayatri
[not found] <20250515164620.071d70e3@canb.auug.org.au>
2025-05-15 8:32 ` Ilpo Järvinen
2025-05-15 9:22 ` Ingo Molnar
2025-05-15 12:19 ` Stephen Rothwell
2025-05-15 12:57 ` Ingo Molnar
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=20110222143434.GA9720@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=malattia@linux.it \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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