From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: make kobj_type structures constant
Date: Tue, 14 Feb 2023 10:07:19 -0800 [thread overview]
Message-ID: <Y+vN18flpTqWwvll@google.com> (raw)
In-Reply-To: <abb12474-f338-dedf-115b-da70e4946cec@kernel.org>
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,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-02-14 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 3:20 [f2fs-dev] [PATCH] f2fs: make kobj_type structures constant Thomas Weißschuh
2023-02-10 21:40 ` patchwork-bot+f2fs
2023-02-13 9:25 ` Chao Yu
2023-02-13 17:51 ` Jaegeuk Kim
2023-02-14 1:42 ` Chao Yu
2023-02-14 18:07 ` Jaegeuk Kim [this message]
2023-02-15 14:43 ` Chao Yu
2023-02-15 17:46 ` Jaegeuk Kim
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=Y+vN18flpTqWwvll@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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).