lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 19 Dec 2015 10:18:06 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Cornelia Huck <cornelia.huck@...ibm.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Christian Borntraeger <borntraeger@...ibm.com>
Subject: Re: [PATCH 20/43] MAINTAINERS: add git URL for KVM/s390

On Fri, Dec 18, 2015 at 01:42:09PM +0100, Cornelia Huck wrote:
> On Fri, 18 Dec 2015 20:32:15 +0800
> Fengguang Wu <fengguang.wu@...el.com> wrote:
> 
> > Thanks! The background is, the 0day patch test script relies on the
> > information in MAINTAINERS to decide which tree it can apply the LKML
> > patches to. So I need to add some missing git URLs to the MAINTAINERS
> > file.
> 
> Don't you also need the branch the patches should apply against, or am
> I misunderstanding what you're trying to do?

Yes one option is to append the branch name in MAINTAINERS like this:

+T:     git git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git next

The other option is to get the branch name from linux-next, whose Next/Trees
file contains this line:

kvms390         git     git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git#next

Then the robot knows patches should be applied to the 'next' branch.

So for most trees, there is no need to specify the branch name in the
MAINTAINERS file. Not only it's not necessary, but also helps avoid
double configuration.

Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ