From: Richard Weinberger <richard@nod.at>
To: Matthew Leach <matthew@mattleach.net>
Cc: linux-kernel@vger.kernel.org, "Martin Pärtel" <martin.partel@gmail.com>
Subject: Re: [REGRESSION] uml: signal.c build errors
Date: Wed, 24 Oct 2012 11:17:42 +0200 [thread overview]
Message-ID: <5087B236.5060804@nod.at> (raw)
In-Reply-To: <87txtkgrsw.fsf@mattleach.net>
On 24.10.2012 11:09, Matthew Leach wrote:
> Hi Richard,
>
> Richard Weinberger <richard@nod.at> writes:
>>
>> Does this patch fix the issue?
>
> Your patch fixed the initial error, but I now get:
Okay, we have to get rid of all struct sig_infos.
A patch is on the way.
Thanks,
//richard
next prev parent reply other threads:[~2012-10-24 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 23:18 [REGRESSION] uml: signal.c build errors Matthew Leach
2012-10-24 8:08 ` Richard Weinberger
2012-10-24 8:10 ` Richard Weinberger
2012-10-24 9:09 ` Matthew Leach
2012-10-24 9:17 ` Richard Weinberger [this message]
2012-12-11 23:15 ` ryanvade
2012-10-24 19:39 ` Richard Weinberger
2012-10-24 19:48 ` Matthew Leach
2012-10-24 19:54 ` Richard Weinberger
2012-10-24 20:06 ` Matthew Leach
2012-10-24 20:09 ` Richard Weinberger
2012-10-24 20:13 ` Matthew Leach
2012-10-24 20:17 ` Richard Weinberger
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=5087B236.5060804@nod.at \
--to=richard@nod.at \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.partel@gmail.com \
--cc=matthew@mattleach.net \
/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