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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 9 Jul 2014 22:17:30 -0700
From:	Olof Johansson <olof@...om.net>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	Mohit KUMAR DCG <Mohit.KUMAR@...com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	Pratyush ANAND <pratyush.anand@...com>,
	"'Bjorn Helgaas' (bhelgaas@...gle.com)" <bhelgaas@...gle.com>,
	spear-devel <spear-devel@...t.st.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Mark Nicholson <mark@...holnet.com>,
	"FTPAdmin Kernel.org" <ftpadmin@...nel.org>
Subject: Re: [GIT PULL] ARM: SPEAr1310 PCIe updates

On Wed, Jul 9, 2014 at 5:18 PM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> On 9 July 2014 23:39, Olof Johansson <olof@...om.net> wrote:
>> * Why are you sending a pull request for a repo that is not yours?
>
> Because Mohit/Pratyush were facing some issues in pushing patches
> to the SPEAr public git repo. And so I tried to help them out publicly
> and nobody objected then:
>
> https://lkml.org/lkml/2014/7/8/10

This is completely done wrong on so many levels.

I am not going to merge code from someone who doesn't have the basic
skills down when there's already a maintainer for the platform.
Luckily, you can deal with it -- be it coaching the ST employees on
how to work with the community the right way, or doing the work
yourself to send the code up. Probably a combination in this case.

>> * Why is Viresh the git committer but hasn't signed off on the patches?
>
> I didn't sign-off because I haven't even looked closed at many of the
> patches around PCI and Acked whatever I could understand.

Thanks, good to know that the series hasn't been fully reviewed. That
makes me even more hesitant to apply it at the moment, given all the
other issues around it.

> But yeah, this committer thing is what I missed. Because of that I might
> be required to signoff it.

Anyone touching the patch, forwarding it or applying it needs to sign
off. It's quite simple, and well documented.

>> Are you sharing accounts on kernel.org? (Adding kernel.org admin on cc
>> just in case).
>
> Obviously not. I am alone the user of this account.

Good.


-Olof
--
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