From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Xie Yongji <xieyongji@bytedance.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] vduse: make vduse_class constant
Date: Sun, 8 Oct 2023 02:41:22 -0400 [thread overview]
Message-ID: <20231008024039-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2023100823-absurd-imitation-092d@gregkh>
On Sun, Oct 08, 2023 at 08:40:05AM +0200, Greg Kroah-Hartman wrote:
> On Sun, Oct 08, 2023 at 02:20:52AM -0400, Michael S. Tsirkin wrote:
> > On Fri, Oct 06, 2023 at 04:30:44PM +0200, Greg Kroah-Hartman wrote:
> > > Now that the driver core allows for struct class to be in read-only
> > > memory, we should make all 'class' structures declared at build time
> > > placing them into read-only memory, instead of having to be dynamically
> > > allocated at runtime.
> > >
> > > Cc: "Michael S. Tsirkin" <mst@redhat.com>
> > > Cc: Jason Wang <jasowang@redhat.com>
> > > Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > > Cc: Xie Yongji <xieyongji@bytedance.com>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >
> > Acked-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > Greg should I merge it or do you intend to merge all these patches?
>
> "all"? There's loads of them for all sorts of subsystems, so feel free
> to take it through your subsystem tree if you want. I usually scoop up
> the ones that no one picks after a release and take them through my
> tree, to pick up the stragglers.
>
> So it's your call, whatever is easier for you is fine for me.
>
> thanks,
>
> greg k-h
To clarify which commit does this depend on?
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Xie Yongji <xieyongji@bytedance.com>
Subject: Re: [PATCH] vduse: make vduse_class constant
Date: Sun, 8 Oct 2023 02:41:22 -0400 [thread overview]
Message-ID: <20231008024039-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2023100823-absurd-imitation-092d@gregkh>
On Sun, Oct 08, 2023 at 08:40:05AM +0200, Greg Kroah-Hartman wrote:
> On Sun, Oct 08, 2023 at 02:20:52AM -0400, Michael S. Tsirkin wrote:
> > On Fri, Oct 06, 2023 at 04:30:44PM +0200, Greg Kroah-Hartman wrote:
> > > Now that the driver core allows for struct class to be in read-only
> > > memory, we should make all 'class' structures declared at build time
> > > placing them into read-only memory, instead of having to be dynamically
> > > allocated at runtime.
> > >
> > > Cc: "Michael S. Tsirkin" <mst@redhat.com>
> > > Cc: Jason Wang <jasowang@redhat.com>
> > > Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > > Cc: Xie Yongji <xieyongji@bytedance.com>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >
> > Acked-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > Greg should I merge it or do you intend to merge all these patches?
>
> "all"? There's loads of them for all sorts of subsystems, so feel free
> to take it through your subsystem tree if you want. I usually scoop up
> the ones that no one picks after a release and take them through my
> tree, to pick up the stragglers.
>
> So it's your call, whatever is easier for you is fine for me.
>
> thanks,
>
> greg k-h
To clarify which commit does this depend on?
--
MST
next prev parent reply other threads:[~2023-10-08 6:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 14:30 [PATCH] vduse: make vduse_class constant Greg Kroah-Hartman
2023-10-06 14:30 ` Greg Kroah-Hartman
2023-10-07 8:21 ` Yongji Xie
2023-10-08 5:28 ` Jason Wang
2023-10-08 5:28 ` Jason Wang
2023-10-08 6:20 ` Michael S. Tsirkin
2023-10-08 6:20 ` Michael S. Tsirkin
2023-10-08 6:40 ` Greg Kroah-Hartman
2023-10-08 6:40 ` Greg Kroah-Hartman
2023-10-08 6:41 ` Michael S. Tsirkin [this message]
2023-10-08 6:41 ` Michael S. Tsirkin
2023-10-08 6:46 ` Greg Kroah-Hartman
2023-10-08 6:46 ` Greg Kroah-Hartman
2023-10-08 7:07 ` Michael S. Tsirkin
2023-10-08 7:07 ` Michael S. Tsirkin
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=20231008024039-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.com \
--cc=xuanzhuo@linux.alibaba.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.