Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: kernel test robot <lkp@intel.com>, <stable@vger.kernel.org>,
	<oe-kbuild-all@lists.linux.dev>
Subject: Re: [PATCH 5.4 09/17] xfs: simplify a check in xfs_ioctl_setattr_check_cowextsize
Date: Wed, 12 Apr 2023 12:47:16 +0800	[thread overview]
Message-ID: <ZDY31JiLR2k0M2dP@rli9-mobl> (raw)
In-Reply-To: <87cz49lnjz.fsf@debian-BULLSEYE-live-builder-AMD64>

On Wed, Apr 12, 2023 at 10:06:59AM +0530, Chandan Babu R wrote:
> On Wed, Apr 12, 2023 at 12:29:27 PM +0800, kernel test robot wrote:
> > Hi,
> >
> > Thanks for your patch.
> >
> > FYI: kernel test robot notices the stable kernel rule is not satisfied.
> >
> > Rule: 'Cc: stable@vger.kernel.org' or 'commit <sha1> upstream.'
> 
> I have CCed stable@vger.kernel.org and also mentioned the upstream commit ID
> in the commit message.

Hi Chandan, this looks to be a typo of "uptream" in your changelog

commit 5e28aafe708ba3e388f92a7148093319d3521c2f uptream.

Thanks

> 
> > Subject: [PATCH 5.4 09/17] xfs: simplify a check in xfs_ioctl_setattr_check_cowextsize
> > Link: https://lore.kernel.org/stable/20230412042624.600511-10-chandan.babu%40oracle.com
> >
> > The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> 
> -- 
> chandan
> 

  reply	other threads:[~2023-04-12  4:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  4:26 [PATCH 5.4 00/17] xfs stable candidate patches for 5.4.y (from v5.11 & v5.12) Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 01/17] xfs: show the proper user quota options Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 02/17] xfs: merge the projid fields in struct xfs_icdinode Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 03/17] xfs: ensure that the inode uid/gid match values match the icdinode ones Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 04/17] xfs: remove the icdinode di_uid/di_gid members Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 05/17] xfs: remove the kuid/kgid conversion wrappers Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 06/17] xfs: add a new xfs_sb_version_has_v3inode helper Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 07/17] xfs: only check the superblock version for dinode size calculation Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 08/17] xfs: simplify di_flags2 inheritance in xfs_ialloc Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 09/17] xfs: simplify a check in xfs_ioctl_setattr_check_cowextsize Chandan Babu R
2023-04-12  4:29   ` kernel test robot
2023-04-12  4:36     ` Chandan Babu R
2023-04-12  4:47       ` Philip Li [this message]
2023-04-12  4:50         ` Chandan Babu R
2023-04-12  5:08   ` [PATCH 5.4 V2] " Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 10/17] xfs: remove the di_version field from struct icdinode Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 11/17] xfs: fix up non-directory creation in SGID directories Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 12/17] xfs: set inode size after creating symlink Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 13/17] xfs: report corruption only as a regular error Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 14/17] xfs: shut down the filesystem if we screw up quota reservation Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 15/17] xfs: consider shutdown in bmapbt cursor delete assert Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 16/17] xfs: don't reuse busy extents on extent trim Chandan Babu R
2023-04-12  4:26 ` [PATCH 5.4 17/17] xfs: force log and push AIL to clear pinned inodes when aborting mount Chandan Babu R
2023-04-18  9:49 ` [PATCH 5.4 00/17] xfs stable candidate patches for 5.4.y (from v5.11 & v5.12) Greg KH
2023-04-18 10:53   ` Greg KH
2023-04-18 12:39     ` Chandan Babu R

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=ZDY31JiLR2k0M2dP@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=chandan.babu@oracle.com \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox