On Tue, Nov 26, 2024 at 8:22 PM Matthew Wilcox wrote:
>
> On Tue, Nov 26, 2024 at 06:57:20PM -0800, Yuanchu Xie wrote:
> > diff --git a/mm/internal.h b/mm/internal.h
> > index 64c2eb0b160e..bbd3c1501bac 100644
> > --- a/mm/internal.h
> > +++ b/mm/internal.h
> > @@ -470,9 +470,14 @@ extern unsigned
On Tue, Nov 19, 2024 at 11:49:07AM +0100, Roberto Sassu wrote:
Hi Roberto, I hope the week is going well for you.
> From: Roberto Sassu
>
> Integrity detection and protection has long been a desirable feature, to
> reach a large user base and mitigate the risk of flaws in the software
> and att
+ da...@lists.linux.dev
I haven't thoroughly read any version of this patch series due to my laziness,
sorry. So I may saying something completely wrong. My apology in advance, and
please correct me in the case.
> On Tue, Nov 26, 2024 at 06:57:19PM -0800, Yuanchu Xie wrote:
> > This patch serie
On Wed, Nov 27, 2024 at 10:51:11AM +0100, Roberto Sassu wrote:
> For eBPF programs we are also in a need for a better way to
> measure/appraise them.
I am confused now, I was under the impression this "Integrity Digest
Cache" is just a special thing for LSMs, and so I was under the
impression that
On Wed, Nov 27, 2024 at 12:54:15PM +0100, Mauro Carvalho Chehab wrote:
> Em Wed, 27 Nov 2024 10:39:48 +0100 Mauro Carvalho Chehab escreveu:
>
> > > This workflow doesn't apply to patch submitters who are not allowed to
> > > send pull requests and who don't have direct commit access. I thought
> >
Em Wed, 27 Nov 2024 15:39:38 +0200
Laurent Pinchart escreveu:
> On Wed, Nov 27, 2024 at 12:54:15PM +0100, Mauro Carvalho Chehab wrote:
> > Em Wed, 27 Nov 2024 10:39:48 +0100 Mauro Carvalho Chehab escreveu:
> >
> > > > This workflow doesn't apply to patch submitters who are not allowed to
> > >
Jumping in the middle here with some clarifications.
On Wed, 27 Nov 2024 at 12:19, Laurent Pinchart
wrote:
> On Wed, Nov 27, 2024 at 10:39:48AM +0100, Mauro Carvalho Chehab wrote:
> > It is somewhat similar to drm-intel and drm-xe, where reviews are part
> > of the acceptance criteria to become
Hi Mike,
Sorry for reviving a rather old thread.
On Wed, 07 Aug 2024 07:41:08 +0100,
Mike Rapoport wrote:
>
> From: "Mike Rapoport (Microsoft)"
>
> Until now arch_numa was directly translating firmware NUMA information
> to memblock.
>
> Using numa_memblks as an intermediate step has a few a
On Wed, 2024-11-27 at 11:30 -0600, Dr. Greg wrote:
> On Tue, Nov 19, 2024 at 11:49:07AM +0100, Roberto Sassu wrote:
>
> Hi Roberto, I hope the week is going well for you.
>
> > From: Roberto Sassu
> >
> > Integrity detection and protection has long been a desirable feature, to
> > reach a large
On Wed, Nov 27, 2024 at 04:09:23PM +0100, Mauro Carvalho Chehab wrote:
> Em Wed, 27 Nov 2024 15:39:38 +0200 Laurent Pinchart escreveu:
> > On Wed, Nov 27, 2024 at 12:54:15PM +0100, Mauro Carvalho Chehab wrote:
> > > Em Wed, 27 Nov 2024 10:39:48 +0100 Mauro Carvalho Chehab escreveu:
> > >
> > > >
On Wed, Nov 27, 2024 at 12:26 AM Johannes Weiner wrote:
>
> On Tue, Nov 26, 2024 at 06:57:19PM -0800, Yuanchu Xie wrote:
> > This patch series provides workingset reporting of user pages in
> > lruvecs, of which coldness can be tracked by accessed bits and fd
> > references. However, the concept o
On Tue, Nov 26, 2024 at 7:00 PM Yuanchu Xie wrote:
[...]
> diff --git a/include/linux/workingset_report.h
> b/include/linux/workingset_report.h
> index f6bbde2a04c3..1074b89035e9 100644
> --- a/include/linux/workingset_report.h
> +++ b/include/linux/workingset_report.h
[...]
> diff --git a/includ
On Wed, Nov 27, 2024 at 3:15 PM Daniel Verkamp wrote:
> > * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
> > WAY
> > * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
> > * SUCH DAMAGE. */
> > +#include "linux/workingset_report.h"
> > #includ
Em Tue, 26 Nov 2024 17:19:30 +0200
Laurent Pinchart escreveu:
> Hi Mauro and Hans,
>
> On Mon, Nov 25, 2024 at 02:28:58PM +0100, Mauro Carvalho Chehab wrote:
> > As the media subsystem will experiment with a multi-committers model,
> > update the Maintainer's entry profile to the new rules, and
On Tue, 2024-11-26 at 11:04 -0800, Luis Chamberlain wrote:
> On Tue, Nov 26, 2024 at 11:25:07AM +0100, Roberto Sassu wrote:
> > On Mon, 2024-11-25 at 15:53 -0800, Luis Chamberlain wrote:
> >
> > Firmware, eBPF programs and so on are supposed
>
> Keyword: "supposed".
It depends if they are in a
Tested-by: Yangyu Chen
I applied and tested it on Nezha hardware, and it works fine.
Cheers,
Yangyu Chen
On 11/14/24 10:21, Charlie Jenkins wrote:
xtheadvector is a custom extension that is based upon riscv vector
version 0.7.1 [1]. All of the vector routines have been modified to
support thi
Hi Laurent,
Thank you for your constructive feedback! In my reply I didn't comment on your
trivial changes like grammar/spelling, unless otherwise noted I'm OK with those.
On 26/11/2024 16:19, Laurent Pinchart wrote:
> Hi Mauro and Hans,
>
> On Mon, Nov 25, 2024 at 02:28:58PM +0100, Mauro Carval
On Wed, Nov 27, 2024 at 10:39:48AM +0100, Mauro Carvalho Chehab wrote:
> Em Tue, 26 Nov 2024 17:19:30 +0200 Laurent Pinchart escreveu:
> > On Mon, Nov 25, 2024 at 02:28:58PM +0100, Mauro Carvalho Chehab wrote:
> > > As the media subsystem will experiment with a multi-committers model,
> > > update
Em Wed, 27 Nov 2024 10:39:48 +0100
Mauro Carvalho Chehab escreveu:
> > This workflow doesn't apply to patch submitters who are not allowed to
> > send pull requests and who don't have direct commit access. I thought
> > these submitters are the main audience of this document. In that case, I
> >
Hi Hans,
On Wed, Nov 27, 2024 at 12:59:58PM +0100, Hans Verkuil wrote:
> Hi Laurent,
>
> Thank you for your constructive feedback! In my reply I didn't comment on your
> trivial changes like grammar/spelling, unless otherwise noted I'm OK with
> those.
Some of the points you raised are also dis
20 matches
Mail list logo
