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]
Message-ID: <CAJe_ZhdR_aTU1BCLsHYCxnaWs8AE+BEf4P18B_Mi==8kVO9qCQ@mail.gmail.com>
Date:	Tue, 21 Oct 2014 14:40:48 +0530
From:	Jassi Brar <jaswinder.singh@...aro.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	torvalds@...ux-foundation.org,
	Ashwin Chaugule <ashwin.chaugule@...aro.org>,
	"ks.giri@...sung.com" <ks.giri@...sung.com>,
	Matt Porter <mporter@...aro.org>,
	LeyFoon Tan <lftan.linux@...il.com>,
	"Anna, Suman" <s-anna@...com>, Bjorn Andersson <bjorn@...o.se>,
	Mark Brown <broonie@...aro.org>,
	Kevin Hilman <khilman@...aro.org>,
	Andy Green <andy.green@...aro.org>,
	Grant Likely <grant.likely@...aro.org>,
	Andrew Bresticker <abrestic@...omium.org>,
	Sudeep Holla <sudeep.holla@....com>,
	"Ira W. Snyder" <iws@...o.caltech.edu>,
	Alexandre Torgue <alexandre.torgue@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] New Mailbox framework for 3.18

On 21 October 2014 13:13, Arnd Bergmann <arnd@...db.de> wrote:
> On Monday 20 October 2014 15:23:38 Jassi Brar wrote:
>> On 8 October 2014 11:09, Jassi Brar <jaswinder.singh@...aro.org> wrote:
>> > Hi Linus,
>> >
>> > A framework for Mailbox controllers and clients have been cooking for
>> > more than a year now. Everybody in the CC list had been copied on
>> > patchset revisions and most of them have made sounds of approval,
>> > though just one concrete Reviewed-by. The patchset has also been in
>> > linux-next for a couple of weeks now and no conflict has been
>> > reported. The framework has the backing of at least 5 platforms,
>> > though I can't say if/when they upstream their drivers (some
>> > businesses have 'changed').
>> >
>> Hi Linus,
>>   While I was speculating on the reasons why you were not merging the
>> patchset - not enough Acked-Bys, you want it via asoc, my git server
>> down (I am not aware) or you just forgot in the unlikely case - I
>> missed the window.
>>  There are couple of platforms waiting for the api to get upstream and
>> now I have the devs on my back. Assuming I messed up the pull request
>> somehow, may I know how?
>
> Jassi,
>
> I assume a contributing factor here was that you rebased the tree
> just before submission, which is always a bad sign.
>
> There is a small chance that Linus will still pull this for v3.18, as he
> said that he'd take a few things that have been submitted in time. If
> not, please rebase once more on top of v3.18-rc1 and send a pull request
> to arm@...nel.org so we can put it into arm-soc for 3.19.
>
OK, I will. And thanks for pointing out the issue with rebasing.

Thanks
Jassi
--
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