public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: nathan@kernel.org, marcus.folkesson@gmail.com,
	cuigaosheng1@huawei.com, andriy.shevchenko@linux.intel.com,
	m.szyprowski@samsung.com, jack@suse.cz, stable@vger.kernel.org,
	patches@lists.linux.dev, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, jonathanh@nvidia.com,
	f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 4.9 000/251] 4.9.337-rc1 review
Date: Sat, 7 Jan 2023 11:27:48 +0100	[thread overview]
Message-ID: <Y7lJJEhK3W3joZv6@kroah.com> (raw)
In-Reply-To: <Y7cpWKbQlNW5qEeO@duo.ucw.cz>

On Thu, Jan 05, 2023 at 08:47:36PM +0100, Pavel Machek wrote:
> This one is okay in mainline, but contains wrong error handling in the
> 4.9 backport. 4.19 seems okay. It needs to "goto out_unlock", not
> return directly.
> 
> > Jan Kara <jack@suse.cz>
> >     ext4: initialize quota before expanding inode in setproject ioctl

I've fixed this up, good catch.  The rest I've left as they seem
reasonable to be in the tree as-is.

thanks,

greg k-h

  reply	other threads:[~2023-01-07 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 12:52 [PATCH 4.9 000/251] 4.9.337-rc1 review Greg Kroah-Hartman
2023-01-05 16:36 ` Shuah Khan
2023-01-05 19:13 ` Guenter Roeck
2023-01-05 19:17 ` Pavel Machek
2023-01-05 19:28 ` Florian Fainelli
2023-01-05 19:47 ` Pavel Machek
2023-01-07 10:27   ` Greg Kroah-Hartman [this message]
2023-01-06 10:12 ` Naresh Kamboju

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=Y7lJJEhK3W3joZv6@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=cuigaosheng1@huawei.com \
    --cc=f.fainelli@gmail.com \
    --cc=jack@suse.cz \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=m.szyprowski@samsung.com \
    --cc=marcus.folkesson@gmail.com \
    --cc=nathan@kernel.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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