All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Sasha Levin <sashal@kernel.org>
Cc: gregkh@linuxfoundation.org, jack@suse.cz,
	scan-admin@coverity.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ext4: simplify checking quota limits in ext4_statfs()" failed to apply to 5.5-stable tree
Date: Tue, 18 Feb 2020 12:08:01 -0500	[thread overview]
Message-ID: <20200218170801.GD147128@mit.edu> (raw)
In-Reply-To: <20200218163434.GO1734@sasha-vm>

> I'm not quite sure that this patch is stable material.

Yeah, that was a misfire on my part.  I think I had somehow convinced
myself that it was a prereq for another patch that was stable
material, but looking at it again, that's not the case.

	      	      	    	   	  - Ted

  reply	other threads:[~2020-02-18 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 19:07 FAILED: patch "[PATCH] ext4: simplify checking quota limits in ext4_statfs()" failed to apply to 5.5-stable tree gregkh
2020-02-18 16:34 ` Sasha Levin
2020-02-18 17:08   ` Theodore Y. Ts'o [this message]
2020-02-18 18:21     ` Sasha Levin

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=20200218170801.GD147128@mit.edu \
    --to=tytso@mit.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=sashal@kernel.org \
    --cc=scan-admin@coverity.com \
    --cc=stable@vger.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.