From: David Howells <dhowells@redhat.com>
To: Dan Carpenter <error27@gmail.com>
Cc: dhowells@redhat.com, oe-kbuild@lists.linux.dev, lkp@intel.com,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:pending-fixes 135/296] net/rxrpc/call_object.c:303 rxrpc_connect_call() warn: missing error code 'ret'
Date: Wed, 11 Jan 2023 09:03:38 +0000 [thread overview]
Message-ID: <2252769.1673427818@warthog.procyon.org.uk> (raw)
In-Reply-To: <202301111153.9eZRYLf1-lkp@intel.com>
Good catch, thanks. That should be returning -ENOMEM.
David
prev parent reply other threads:[~2023-01-11 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 4:29 Dan Carpenter
2023-01-11 9:03 ` David Howells [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=2252769.1673427818@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=error27@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
/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