On 02/15, Chao Yu wrote:
> On 2023/2/15 2:07, Jaegeuk Kim wrote:
> > 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 <li...@weissschuh.net>
> > > > >
> > > > > Reviewed-by: Chao Yu <c...@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.
>
> Jaegeuk, so why do we need to avoid breaking -next branch? I didn't get it.
> :-(
That's not for linux-next, but my -next work.
>
> >
> > >
> > > 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.
>
> Sure, not problem.
>
> Thanks,
>
> >
> > Thanks,
> >
> > >
> > > Thanks,
> > >
> > > >
> > > > Thanks,
> > > >
> > > > >
> > > > > Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
