similar to: [PATCH 1/2] get_maintainer: create filename-only regex match type

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

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

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]

Hey Folks! I''ve got a Fedora Core 4 machine that I''m installing Ruby on Rails on, following this set of instructions: http://www.digitalmediaminute.com/howto/fc4rails/ Everything has gone well up until I get to the part about configuring lighttpd to use virtual hosts. Here''s the chunk of code I''ve got in my config file that appears to be the culprit.

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

On 05/19/2014 03:24 AM, Alexandre Courbot wrote: > Add the device tree binding documentation for the GK20A GPU used in > Tegra K1 SoCs. A few minor nits, but otherwise, Acked-by: Stephen Warren <swarren at nvidia.com> > diff --git a/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt b/Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt > +Required properties: > +-

I am sorry if this is a bother... I am looking for the PGP/GPG public key that rsync was signed with. I can't find it at samba.org or the rsync web site. Sorry if I am missing something obvious, but would you please point me in the right direction? Thanks in advance for any help. -- ================================= David May Senior UNIX System Administrator Albuquerque TVI 505-224-3015

https://bugzilla.mindrot.org/show_bug.cgi?id=2308 Bug ID: 2308 Summary: Forwarded Unix domain sockets not removed on logout Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at

With the numbers of patches flying around it can be a bit hard for a maintainer to spot patches which (s)he is expected to comment on / deal with, especially now that we have a larger number of maintainers of varying subsystems etc. I think it might be time to start asking patch submitters to CC the maintainers of the code they are touching, based on the MAINTAINERS file. If people (specifically

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

On Tue, Dec 01, 2015 at 06:21:06PM -0800, Sinclair Yeh wrote: > On Tue, Dec 01, 2015 at 04:04:08PM -0800, Greg Kroah-Hartman wrote: > > On Tue, Dec 01, 2015 at 02:54:20PM -0800, Sinclair Yeh wrote: > > > Hi, > > > > > > On Tue, Dec 01, 2015 at 02:45:27PM -0800, Dmitry Torokhov wrote: > > > > On Tue, Dec 1, 2015 at 2:32 PM, Sinclair Yeh <syeh at

On Tue, Dec 01, 2015 at 06:21:06PM -0800, Sinclair Yeh wrote: > On Tue, Dec 01, 2015 at 04:04:08PM -0800, Greg Kroah-Hartman wrote: > > On Tue, Dec 01, 2015 at 02:54:20PM -0800, Sinclair Yeh wrote: > > > Hi, > > > > > > On Tue, Dec 01, 2015 at 02:45:27PM -0800, Dmitry Torokhov wrote: > > > > On Tue, Dec 1, 2015 at 2:32 PM, Sinclair Yeh <syeh at

On Tue, Jan 26, 2016 at 11:32:00AM +0100, Peter Zijlstra wrote: > On Tue, Jan 26, 2016 at 11:24:02AM +0100, Peter Zijlstra wrote: > > > Yeah, this goes under the header: memory-barriers.txt is _NOT_ a > > specification (I seem to keep repeating this). > > Do we want this ? > > --- > Documentation/memory-barriers.txt | 17 +++++++++++++++++ > 1 file changed,

On Tue, Jan 26, 2016 at 11:32:00AM +0100, Peter Zijlstra wrote: > On Tue, Jan 26, 2016 at 11:24:02AM +0100, Peter Zijlstra wrote: > > > Yeah, this goes under the header: memory-barriers.txt is _NOT_ a > > specification (I seem to keep repeating this). > > Do we want this ? > > --- > Documentation/memory-barriers.txt | 17 +++++++++++++++++ > 1 file changed,

On Wed, Dec 02, 2015 at 09:26:34AM -0800, Dmitry Torokhov wrote: > On Wed, Dec 02, 2015 at 07:31:24AM -0800, Greg Kroah-Hartman wrote: > > On Tue, Dec 01, 2015 at 06:21:06PM -0800, Sinclair Yeh wrote: > > > On Tue, Dec 01, 2015 at 04:04:08PM -0800, Greg Kroah-Hartman wrote: > > > > On Tue, Dec 01, 2015 at 02:54:20PM -0800, Sinclair Yeh wrote: > > > > >

On Wed, Dec 02, 2015 at 09:26:34AM -0800, Dmitry Torokhov wrote: > On Wed, Dec 02, 2015 at 07:31:24AM -0800, Greg Kroah-Hartman wrote: > > On Tue, Dec 01, 2015 at 06:21:06PM -0800, Sinclair Yeh wrote: > > > On Tue, Dec 01, 2015 at 04:04:08PM -0800, Greg Kroah-Hartman wrote: > > > > On Tue, Dec 01, 2015 at 02:54:20PM -0800, Sinclair Yeh wrote: > > > > >

On Wed, 2013-09-04 at 14:23 +0530, Alok Kataria wrote: > 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. It never hurts to add MAINTAINER entries. > If you are thinking why do this now, off late we have seen quite a few > changes that touched the