From: Jason Wang <jasowang@redhat.com>
To: Patrick Venture <venture@google.com>
Cc: Peter Foley <pefoley@google.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Set return code on failure
Date: Wed, 5 Jan 2022 11:16:10 +0800 [thread overview]
Message-ID: <CACGkMEuMuvR73s4QFq3jNP-e5V-EZ+mwzCfXLY4jnaLrs0BaXA@mail.gmail.com> (raw)
In-Reply-To: <CAO=notzyC8icquKrrQZMJRZ5Dqvh3rj0OMw+A1_6iMUTbjSCHw@mail.gmail.com>
On Wed, Jan 5, 2022 at 5:32 AM Patrick Venture <venture@google.com> wrote:
>
>
>
> On Tue, Jan 4, 2022 at 1:18 PM Patrick Venture <venture@google.com> wrote:
>>
>> From: Peter Foley <pefoley@google.com>
>>
>> Match the other error handling in this function.
>
>
> Just noticed I didn't fix up the commit title here to match style. Should I do a PATCH RESEND or a new patch, or can you add the "net/tap: " to the title before applying (should it be accepted).
Please resend.
Thanks
>
>>
>>
>> Signed-off-by: Peter Foley <pefoley@google.com>
>
> Reviewed-by: Patrick Venture <venture@google.com>
>>
>> ---
>> net/tap.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/net/tap.c b/net/tap.c
>> index f716be3e3f..c5cbeaa7a2 100644
>> --- a/net/tap.c
>> +++ b/net/tap.c
>> @@ -900,6 +900,7 @@ int net_init_tap(const Netdev *netdev, const char *name,
>> if (i == 0) {
>> vnet_hdr = tap_probe_vnet_hdr(fd, errp);
>> if (vnet_hdr < 0) {
>> + ret = -1;
>> goto free_fail;
>> }
>> } else if (vnet_hdr != tap_probe_vnet_hdr(fd, NULL)) {
>> --
>> 2.34.1.448.ga2b2bfdf31-goog
>>
next prev parent reply other threads:[~2022-01-05 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 21:18 [PATCH] Set return code on failure Patrick Venture
2022-01-04 21:32 ` Patrick Venture
2022-01-05 3:16 ` Jason Wang [this message]
2022-01-04 21:46 ` [PATCH] net/tap: " Philippe Mathieu-Daudé
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=CACGkMEuMuvR73s4QFq3jNP-e5V-EZ+mwzCfXLY4jnaLrs0BaXA@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=pefoley@google.com \
--cc=qemu-devel@nongnu.org \
--cc=venture@google.com \
/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;
as well as URLs for NNTP newsgroup(s).