From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: edac-amd tree build failure
Date: Wed, 20 May 2009 10:20:04 +1000 [thread overview]
Message-ID: <20090520102004.4709567d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090519175426.GC18874@aftab>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
Hi Boris,
On Tue, 19 May 2009 19:54:26 +0200 Borislav Petkov <borislav.petkov@amd.com> wrote:
>
> thanks for reporting, I've added a fix for the build failure and updated
> the #for-next branch for you to pull for the next linux-next release.
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-05-20 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 7:18 linux-next: edac-amd tree build failure Stephen Rothwell
2009-05-19 17:54 ` Borislav Petkov
2009-05-20 0:20 ` Stephen Rothwell [this message]
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=20090520102004.4709567d.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=borislav.petkov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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