similar to: [RFC] CCing MAINTAINERS on patches by default?

I think I might be mad to include that many mailing lists in this patchset... As I explained in [PATCH 1/5], fstests covers more and more fs testing thing, so we always get help from fs specific mailing list, due to they learn about their features and bugs more. Besides that, some folks help to review patches (relevant with them) more often. So I'd like to bring in the similar way of

From: Stephen Warren <swarren at nvidia.com> Create a new N: entry type in MAINTAINERS which performs a regex match against filenames; either those extracted from patch +++ or --- lines, or those specified on the command-line using the -f option. This provides the same benefits as using a K: regex option to match a set of filenames (see commit eb90d08 "get_maintainer: allow keywords

From: Stephen Warren <swarren at nvidia.com> Create a new N: entry type in MAINTAINERS which performs a regex match against filenames; either those extracted from patch +++ or --- lines, or those specified on the command-line using the -f option. This provides the same benefits as using a K: regex option to match a set of filenames (see commit eb90d08 "get_maintainer: allow keywords

From: Stephen Warren <swarren at nvidia.com> Create a new N: entry type in MAINTAINERS which performs a regex match against filenames; either those extracted from patch +++ or --- lines, or those specified on the command-line using the -f option. This provides the same benefits as using a K: regex option to match a set of filenames (see commit eb90d08 "get_maintainer: allow keywords

Hey, This change adds an entry to the maintainers file to explicitly state that any changes to vmware.c should be sent to the authors of the file as well. If you are thinking why do this now, off late we have seen quite a few changes that touched the "arch/x86/kernel/cpu/vmware.c" file but were not directed to me, someone else made me aware of those changes. It could be that my use of

Hey, This change adds an entry to the maintainers file to explicitly state that any changes to vmware.c should be sent to the authors of the file as well. If you are thinking why do this now, off late we have seen quite a few changes that touched the "arch/x86/kernel/cpu/vmware.c" file but were not directed to me, someone else made me aware of those changes. It could be that my use of

Hello, I find a strange behavior. When a machine is slow (or with many debug traces or a qemu vm), a interrupt can occur between the pv_irq_ops initialization and the xen_vcpu[0] initialization. This lead to a problem because some operations in xen_irq_ops use xen_vcpu. I send you a patch to fix that but I''m not quite sure that is the right solution. Regards, Anthoine From

On Thu, Jan 15, 2015 at 03:13:08PM +0100, Michal Hocko wrote: > On Thu 15-01-15 15:44:12, Michael S. Tsirkin wrote: > > On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote: > > > On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > > > > Most of our code has > > > > struct foo { > > > > } > > > > > > > > Fix

On Thu, Jan 15, 2015 at 03:13:08PM +0100, Michal Hocko wrote: > On Thu 15-01-15 15:44:12, Michael S. Tsirkin wrote: > > On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote: > > > On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > > > > Most of our code has > > > > struct foo { > > > > } > > > > > > > > Fix

Hi, Header says: /* * Unmaps the @count pages starting at @start_address, which were mapped by a * call to xc_gntshr_share_*. Never logs. */ int xc_gntshr_munmap(xc_gntshr *xcg, void *start_address, uint32_t count); But implementation calls: static int linux_gntshr_munmap(xc_gntshr *xcg, xc_osdep_handle h, void *start_address, uint32_t count) { return

On Fri, 25 Oct 2019, Martin Storsjö via llvm-dev wrote: > On Thu, 24 Oct 2019, James Y Knight via llvm-dev wrote: > >> We do not want to build supplementary notification systems to make github >> issues send additional emails that it is unable to send itself. We will >> only >> support what GitHub supports. That means: >> - You can subscribe to notification

On Fri, 2005-05-13 at 19:51 -0500, Misha Brukman wrote: > The second one is a "serious policy violation", which isn't as clear to > me what the bug reporter is saying, but it mentions warnings during > doxygen build and missing fonts and related issues that I'm not quite > following. (CCing the bug and thus the submitter) sounds like a missing built-depends, at

For some users on my site I'd like to be able to CC a particular user on all outgoing IMAP mails. Incoming I can do but don't see how to do outgoing. Ideas? Dave -- It is told that such are the aerodynamics and wing loading of the bumblebee that, in principle, it cannot fly...if all this be true...life among bumblebees must bear a remarkable resemblance to life in the United

On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > Hi, > > I''m working on verifying TCP checksums on incoming packets in Mirage, but > I''ve run into a bit of a problem. > > If TCP checksum offload is turned on on a virtual interface (this is the > default), and if the TCP connection is local to the machine, it looks like > Xen does not

Signed-off-by: Wei Liu <wei.liu2@citrix.com> --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index e61c2e8..3c441ce 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9366,6 +9366,7 @@ F: arch/arm64/include/asm/xen/ XEN NETWORK BACKEND DRIVER M: Ian Campbell <ian.campbell@citrix.com> +M: Wei Liu <wei.liu2@citrix.com> L:

And also put my name behind the mainternship. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> --- MAINTAINERS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 0358a3e..e2252fc 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -193,8 +193,9 @@ F: xen/include/xen/iommu.h LINUX (PV_OPS) M: Jeremy Fitzhardinge

On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote: > On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > > Most of our code has > > struct foo { > > } > > > > Fix two instances where balloon is inconsistent. > > I hate to complain but is it really necessary to post such patches to > linux-api? Well it's human to err, so it seems wise to

On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote: > On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > > Most of our code has > > struct foo { > > } > > > > Fix two instances where balloon is inconsistent. > > I hate to complain but is it really necessary to post such patches to > linux-api? Well it's human to err, so it seems wise to

Dropping Tegra ML, it's not the place where Nouveau mails should go. Adding Nouveau ML and Maarten, who probably knows Lockdep+Nouveau best. Am Montag, den 04.03.2013, 22:16 +0100 schrieb Borislav Petkov: > New -rc1, so let the stabilization games begin. > > I see the following on rc1, let me know if you need more info. > > > [ 0.633617]

On Sat, May 14, 2005 at 02:18:26AM +0200, Stefan Strasser wrote: > in case you're interested in having llvm in debian sarge: it was > removed today. I don't know why, but you might want to find out > because sarge is in freeze phase for release next month. Possibly because of these: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=llvm I addressed the first one and fixed it in