From: Rusty Russell <rusty@rustcorp.com.au>
To: Richard Weinberger <richard@nod.at>, 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,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH] Params: Fix parse_args() return code checking
Date: Wed, 12 Nov 2014 16:04:16 +1030 [thread overview]
Message-ID: <87sihpm17r.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1415740441-1042-1-git-send-email-richard@nod.at>
Richard Weinberger <richard@nod.at> writes:
> parse_args() returns beside of NULL also ERR_PTR().
Thanks, already queued in my fixes branch.
Cheers,
Rusty.
next prev parent reply other threads:[~2014-11-12 5:41 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 [this message]
2014-11-12 9:34 ` 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=87sihpm17r.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--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=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.