From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>
Cc: user-mode-linux-user@lists.sourceforge.net,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] um: Use common error handling code in port_listen_fd()
Date: Fri, 20 Oct 2017 18:06:43 +0000 [thread overview]
Message-ID: <1508522803.30181.3.camel@perches.com> (raw)
In-Reply-To: <b16407cf-0caa-ea1d-7997-0e9a231468f3@users.sourceforge.net>
On Fri, 2017-10-20 at 19:29 +0200, SF Markus Elfring wrote:
> arch/um/drivers/port_user.c
If you are going to use multiple labels,
it'd be nicer to rename out: too.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>
Cc: user-mode-linux-user@lists.sourceforge.net,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] um: Use common error handling code in port_listen_fd()
Date: Fri, 20 Oct 2017 11:06:43 -0700 [thread overview]
Message-ID: <1508522803.30181.3.camel@perches.com> (raw)
In-Reply-To: <b16407cf-0caa-ea1d-7997-0e9a231468f3@users.sourceforge.net>
On Fri, 2017-10-20 at 19:29 +0200, SF Markus Elfring wrote:
> arch/um/drivers/port_user.c
If you are going to use multiple labels,
it'd be nicer to rename out: too.
next prev parent reply other threads:[~2017-10-20 18:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 17:29 [PATCH] um: Use common error handling code in port_listen_fd() SF Markus Elfring
2017-10-20 17:29 ` SF Markus Elfring
2017-10-20 18:06 ` Joe Perches [this message]
2017-10-20 18:06 ` Joe Perches
2017-10-20 18:22 ` SF Markus Elfring
2017-10-20 18:22 ` SF Markus Elfring
2017-10-23 8:48 ` [PATCH] " Dan Carpenter
2017-10-23 8:48 ` Dan Carpenter
2017-10-23 9:01 ` SF Markus Elfring
2017-10-23 9:01 ` SF Markus Elfring
2017-10-23 9:10 ` Dan Carpenter
2017-10-23 9:10 ` Dan Carpenter
2017-10-23 9:17 ` SF Markus Elfring
2017-10-23 9:17 ` SF Markus Elfring
2017-10-23 10:28 ` [PATCH] " Markus Trippelsdorf
2017-10-23 10:28 ` Markus Trippelsdorf
2017-10-23 12:04 ` SF Markus Elfring
2017-10-23 12:04 ` SF Markus Elfring
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=1508522803.30181.3.camel@perches.com \
--to=joe@perches.com \
--cc=elfring@users.sourceforge.net \
--cc=jdike@addtoit.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.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 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.