linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gregkh <gregkh@linuxfoundation.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: David Miller <davem@davemloft.net>,
	mkubecek@suse.cz, Networking <netdev@vger.kernel.org>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	rweikusat@mobileactivedefense.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ltp@lists.linux.it, Cyril Hrubis <chrubis@suse.cz>,
	junchi.chen@intel.com, Dmitry Vyukov <dvyukov@google.com>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: RFC: changed error code when binding unix socket twice
Date: Thu, 29 Nov 2018 13:36:50 +0100	[thread overview]
Message-ID: <20181129123650.GI3149@kroah.com> (raw)
In-Reply-To: <20181107155644.GA29531@dell5510>

On Wed, Nov 07, 2018 at 04:56:44PM +0100, Petr Vorel wrote:
> Hi
> 
> > I forgot that 4.1 has ended a while ago. Greg also sometimes still takes patches
> > for 3.18, so that might be a candidate aside from 3.18
> 
> Gregkh, David, does it make sense to you to merge commit 0fb44559ffd6 ("af_unix:
> move unix_mknod() out of bindlock") to 3.18? If yes, please do so.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2018-11-29 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  7:34 RFC: changed error code when binding unix socket twice Michal Kubecek
2018-08-31 11:14 ` Petr Vorel
2018-10-29 13:03   ` Arnd Bergmann
2018-10-29 16:33     ` Petr Vorel
2018-10-29 20:48       ` Arnd Bergmann
2018-11-07 15:56         ` Petr Vorel
2018-11-29 12:36           ` gregkh [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=20181129123650.GI3149@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=chrubis@suse.cz \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=junchi.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=mkubecek@suse.cz \
    --cc=naresh.kamboju@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=pvorel@suse.cz \
    --cc=rweikusat@mobileactivedefense.com \
    --cc=xiyou.wangcong@gmail.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).