From: "Theodore Ts'o" <tytso@mit.edu>
To: Sasha Levin <sashal@kernel.org>
Cc: Pavel Machek <pavel@denx.de>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.10 9/9] ext4: enable the lazy init thread when remounting read/write
Date: Tue, 20 Jun 2023 18:25:56 -0400 [thread overview]
Message-ID: <20230620222556.GJ286961@mit.edu> (raw)
In-Reply-To: <ZJG7GyeSa2xZ89/H@sashalap>
On Tue, Jun 20, 2023 at 10:43:39AM -0400, Sasha Levin wrote:
> > Normally "Fixes" would be "Fixes:" and in the signed-off block. Plus,
> > two consecutive sign-offs from tytso are probably wrong, too.
>
> I'm really not sure what you want us to do here, or in other places
> where you've commented about issues with the upstream patch...
Yeah, those were issues with the upstream commit. Sorry about that.
I personally don't care about whether you "clean up" the commit before
having it land in the LTS kernels or leave it as it as originally
commited to upstream, but then again, I'm not the kind of person who
asks whether there's a hyphen in "anal-retentive". (I'm given to
understand it depends on whether the phrase is being used as an
attributive or predicative adjective. :-)
- Ted
prev parent reply other threads:[~2023-06-20 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 11:39 [PATCH AUTOSEL 5.10 1/9] regmap: Account for register length when chunking Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 2/9] scsi: target: iscsi: Prevent login threads from racing between each other Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 3/9] HID: google: add jewel USB id Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 4/9] HID: wacom: Add error check to wacom_parse_and_register() Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 5/9] arm64: Add missing Set/Way CMO encodings Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 6/9] media: cec: core: don't set last_initiator if tx in progress Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 7/9] nfcsim.c: Fix error checking for debugfs_create_dir Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 8/9] usb: gadget: udc: fix NULL dereference in remove() Sasha Levin
2023-06-15 11:39 ` [PATCH AUTOSEL 5.10 9/9] ext4: enable the lazy init thread when remounting read/write Sasha Levin
2023-06-16 19:41 ` Pavel Machek
2023-06-20 14:43 ` Sasha Levin
2023-06-20 22:25 ` Theodore Ts'o [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=20230620222556.GJ286961@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@denx.de \
--cc=sashal@kernel.org \
--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