Date:   Tue, 14 Feb 2023 10:07:19 -0800
From:   Jaegeuk Kim <jaegeuk@kernel.org>
To:     Chao Yu <chao@kernel.org>
Cc:     Thomas =?iso-8859-1?Q?Wei=DFschuh?= <linux@weissschuh.net>,
        linux-f2fs-devel@lists.sourceforge.net,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: make kobj_type structures constant
Message-ID: <Y+vN18flpTqWwvll@google.com>
References: <20230209-kobj_type-f2fs-v1-1-b6feedbdd4a8@weissschuh.net>
 <cc338b66-f0f5-d9b7-81d3-b15bccc9d463@kernel.org>
 <Y+p4jezz5asWoPhu@google.com>
 <abb12474-f338-dedf-115b-da70e4946cec@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <abb12474-f338-dedf-115b-da70e4946cec@kernel.org>
Precedence: bulk

On 02/14, Chao Yu wrote:
> On 2023/2/14 1:51, Jaegeuk Kim wrote:
> > On 02/13, Chao Yu wrote:
> > > On 2023/2/9 11:20, Thomas Wei?schuh wrote:
> > > > Since commit ee6d3dd4ed48 ("driver core: make kobj_type constant.")
> > > > the driver core allows the usage of const struct kobj_type.
> > > > 
> > > > Take advantage of this to constify the structure definitions to prevent
> > > > modification at runtime.
> > > > 
> > > > Signed-off-by: Thomas Wei?schuh <linux@weissschuh.net>
> > > 
> > > Reviewed-by: Chao Yu <chao@kernel.org>
> > 
> > Hi Chao,
> > 
> > Note that, next time, I won't apply/modify any patches merged in -dev,
> > unless it has a problem.
> 
> Hi Jaegeuk,
> 
> Oh, any particular reason, to avoid unneeded commit id change when the time is
> close to merge window?

Hi Chao,

I'm trying to avoid breaking the -next branch.

> 
> Is there any period of grace before merging patches from dev-test branch into dev
> branch? Maybe a week is reasonable? so I may have time to catch up in time.

No rule, but I'm trying to wait for several days while running my local tests.
If the patch looks okay, sometimes I'll queue it right away.

Thanks,

> 
> Thanks,
> 
> > 
> > Thanks,
> > 
> > > 
> > > Thanks,