All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	cgroups <cgroups@vger.kernel.org>,
	Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Chris Metcalf <cmetcalf@ezchip.com>
Subject: Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup
Date: Fri, 19 Jan 2018 09:35:39 -0800	[thread overview]
Message-ID: <CA+55aFwtAfvuBpiDTvwzr8E43jk5y0ZRMAHS273K1Uv_RJNjRw@mail.gmail.com> (raw)
In-Reply-To: <20180119173141.GF3460072@devbig577.frc2.facebook.com>

On Fri, Jan 19, 2018 at 9:31 AM, Tejun Heo <tj@kernel.org> wrote:
>
> I see.  I'll push it your way together with other cgroup changes once
> the merge window opens.

NP. This was a fairly unusual late rc window. It's normally quiet this
period, but first I was distracted by some of the Spectre detail
discussions, and then we had a few other random odd things come in, so
instead of using this week for going through my queues, I was spending
it more on discussion.

But the strscpy patch makes just as much - or more - in the 5.16 merge
window anyway, so it's all good.

              Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
	cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Ma Shimiao
	<mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>,
	Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	Chris Metcalf <cmetcalf-d5a29ZRxExrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup
Date: Fri, 19 Jan 2018 09:35:39 -0800	[thread overview]
Message-ID: <CA+55aFwtAfvuBpiDTvwzr8E43jk5y0ZRMAHS273K1Uv_RJNjRw@mail.gmail.com> (raw)
In-Reply-To: <20180119173141.GF3460072-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>

On Fri, Jan 19, 2018 at 9:31 AM, Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>
> I see.  I'll push it your way together with other cgroup changes once
> the merge window opens.

NP. This was a fairly unusual late rc window. It's normally quiet this
period, but first I was distracted by some of the Spectre detail
discussions, and then we had a few other random odd things come in, so
instead of using this week for going through my queues, I was spending
it more on discussion.

But the strscpy patch makes just as much - or more - in the 5.16 merge
window anyway, so it's all good.

              Linus

  reply	other threads:[~2018-01-19 17:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 14:52 [GIT PULL] cgroup fixes for v4.15-rc7 Tejun Heo
2018-01-08 19:20 ` Linus Torvalds
2018-01-08 19:20   ` Linus Torvalds
2018-01-08 19:23   ` Linus Torvalds
2018-01-08 19:28     ` Tejun Heo
2018-01-08 19:28       ` Tejun Heo
2018-01-08 19:41       ` Linus Torvalds
2018-01-09 15:21         ` [PATCH] string: drop __must_check from strscpy() and restore strscpy() usages in cgroup Tejun Heo
2018-01-09 15:21           ` Tejun Heo
2018-01-12 19:38           ` Tejun Heo
2018-01-19 16:50           ` Tejun Heo
2018-01-19 16:50             ` Tejun Heo
2018-01-19 17:27             ` Linus Torvalds
2018-01-19 17:27               ` Linus Torvalds
2018-01-19 17:31               ` Tejun Heo
2018-01-19 17:35                 ` Linus Torvalds [this message]
2018-01-19 17:35                   ` Linus Torvalds

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=CA+55aFwtAfvuBpiDTvwzr8E43jk5y0ZRMAHS273K1Uv_RJNjRw@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=cgroups@vger.kernel.org \
    --cc=cmetcalf@ezchip.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mashimiao.fnst@cn.fujitsu.com \
    --cc=tj@kernel.org \
    /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.