From: Sasha Levin <sashal@kernel.org>
To: dsterba@suse.cz, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Liu Bo <bo.liu@linux.alibaba.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 028/237] Btrfs: fix alignment in declaration and prototype of btrfs_get_extent
Date: Mon, 25 Nov 2019 09:01:21 -0500 [thread overview]
Message-ID: <20191125140121.GD5861@sasha-vm> (raw)
In-Reply-To: <20191118111143.GE3001@twin.jikos.cz>
On Mon, Nov 18, 2019 at 12:11:43PM +0100, David Sterba wrote:
>On Sat, Nov 16, 2019 at 10:37:43AM -0500, Sasha Levin wrote:
>> From: Liu Bo <bo.liu@linux.alibaba.com>
>>
>> [ Upstream commit de2c6615dcddf2af868c5cbd1db2e9e73b4beb58 ]
>>
>> This fixes btrfs_get_extent to be consistent with our existing
>> declaration style.
>
>The patch is pure white space fix with no effects. I don't see that it
>would be needed for a followup patch. What was the reason to add it to
>autosel/stable ?
Oh I grabbed it as a dependency for a follow up patch which I ended up
dropping, and forgot this one in. I'll drop it as well, sorry for the
noise.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-11-25 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191116154113.7417-1-sashal@kernel.org>
2019-11-16 15:37 ` [PATCH AUTOSEL 4.19 027/237] btrfs: defrag: use btrfs_mod_outstanding_extents in cluster_pages_for_defrag Sasha Levin
2019-11-16 15:37 ` [PATCH AUTOSEL 4.19 028/237] Btrfs: fix alignment in declaration and prototype of btrfs_get_extent Sasha Levin
2019-11-18 11:11 ` David Sterba
2019-11-25 14:01 ` Sasha Levin [this message]
2019-11-16 15:37 ` [PATCH AUTOSEL 4.19 029/237] btrfs: handle error of get_old_root Sasha Levin
2019-11-16 15:40 ` [PATCH AUTOSEL 4.19 195/237] btrfs: avoid link error with CONFIG_NO_AUTO_INLINE 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=20191125140121.GD5861@sasha-vm \
--to=sashal@kernel.org \
--cc=bo.liu@linux.alibaba.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).