From: Richard Weinberger <richard@nod.at>
To: Rusty Russell <rusty@rustcorp.com.au>, akpm@linux-foundation.org
Cc: geert@linux-m68k.org, peterz@infradead.org, hpa@zytor.com,
oleg@redhat.com, kirill.shutemov@linux.intel.com,
prarit@redhat.com, michael.opdenacker@free-electrons.com,
fabf@skynet.be, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Params: Fix parse_args() return code checking
Date: Wed, 12 Nov 2014 10:34:39 +0100 [thread overview]
Message-ID: <546329AF.1070109@nod.at> (raw)
In-Reply-To: <87sihpm17r.fsf@rustcorp.com.au>
Am 12.11.2014 um 06:34 schrieb Rusty Russell:
> Richard Weinberger <richard@nod.at> writes:
>> parse_args() returns beside of NULL also ERR_PTR().
>
> Thanks, already queued in my fixes branch.
I *love* double fixes. ;)
Thanks,
//richard
prev parent reply other threads:[~2014-11-12 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 21:14 [PATCH] Params: Fix parse_args() return code checking Richard Weinberger
2014-11-12 5:34 ` Rusty Russell
2014-11-12 9:34 ` Richard Weinberger [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=546329AF.1070109@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=rusty@rustcorp.com.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