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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 15 Jan 2015 15:51:39 -0500
From:	Jason Cooper <jason@...edaemon.net>
To:	Mark Brown <broonie@...nel.org>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	Grant Likely <grant.likely@...aro.org>,
	Will Deacon <Will.Deacon@....com>,
	"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
	Mark Rutland <Mark.Rutland@....com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
	"graeme.gregory@...aro.org" <graeme.gregory@...aro.org>,
	Sudeep Holla <Sudeep.Holla@....com>,
	"jcm@...hat.com" <jcm@...hat.com>,
	Marc Zyngier <Marc.Zyngier@....com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Rob Herring <robh@...nel.org>,
	Robert Richter <rric@...nel.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Charles Garcia-Tobin <Charles.Garcia-Tobin@....com>,
	"phoenix.liyi@...wei.com" <phoenix.liyi@...wei.com>,
	Timur Tabi <timur@...eaurora.org>,
	"suravee.suthikulpanit@....com" <suravee.suthikulpanit@....com>,
	Yijing Wang <wangyijing@...wei.com>,
	ACPI Devel Mailing List <linux-acpi@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linaro-acpi <linaro-acpi@...ts.linaro.org>
Subject: Re: [PATCH v7 00/17] Introduce ACPI for ARM64 based on ACPI 5.1

On Thu, Jan 15, 2015 at 08:31:59PM +0000, Mark Brown wrote:
> On Thu, Jan 15, 2015 at 03:04:37PM -0500, Jason Cooper wrote:
> > On Thu, Jan 15, 2015 at 07:02:20PM +0000, Mark Brown wrote:
> 
> > > There's probably a bit of a process problem here - these patches are all
> > > being posted as part of big and apparently controversial threads with
> > > subject lines in the form "ARM / ACPI:" so people could be forgiven for
> > > just not even reading the e-mails enough to notice changes to their
> > > subsystems.  Is it worth posting those patches separately more directly
> > > to the relevant maintainers?
> 
> > I think it's beneficial to post the entire series as one thread, but to
> > change the subject line of each patch to adequately reflect the affected
> > subsystem.
> 
> Just changing the subject lines to be more suitable would help, but
> given the painful thread it's probably worth going the extra step if
> the lack of these reviews is a causing problems - I know that even with
> a suitable subject line if I'm busy then I'm fairly likely to zone out
> something in the middle a big series that doesn't seem to be going
> anywhere.

True, I was merely expressing a preference.  A lot of series containing
irqchip changes tend to have build dependencies outside of
drivers/irqchip. So I like to see the whole picture to decide how best
to handle the patches.

I suppose the ideal solution would be to have a "mute sub-thread" option
in the MUA.  But that doesn't help us today.  :)

Whichever way they do it is fine by me.

thx,

Jason.
--
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