linaro-android

linaro-android@lists.linaro.org

1071 discussions

REG:xt_qtaguid: check xt_sock socket before releasing

by subashab＠codeaurora.org

Hi Amit Does this patch ("xt_qtaguid: check xt_sock socket before releasing") need to be ported to 4.4 Android kernel and AOSP kernel? I can see that this is part of 3.18 Linaro tree only. https://git.linaro.org/kernel/linux-linaro-stable.git/blobdiff/6a0ebc2aaaa0… -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

7 years, 10 months

Re: [Linaro] Comment posted to request #SYS-55: Can not submit changes on android-patchsets.git to dev-private-review.linaro.org for review

by YongQin Liu

Hi, Paul, Andy On 2 July 2016 at 03:58, John Stultz <john.stultz(a)linaro.org> wrote: > > Would it make more sense to have gerrit reject new refs/for/ names that > don't correlate to a existing branch? > Is it possible from the server side? Thanks, Yongqin Liu > On Jul 1, 2016 12:41 PM, "YongQin Liu" <yongqin.liu(a)linaro.org> wrote: > >> Hi, Bero, Satish >> >> When you submit changes on android-patchsets repository to dev-private- >> *review*.linaro.org for review, >> please run >> >> *git review* >> >> to submit your changes for review, we have .gitreview file in the >> repository for using that command. >> >> To use "git review", git-review package needs to be installed with >> commands like this: >> >> *sudo apt-get install git-review* >> >> >> Thanks, >> Yongqin Liu >> On 1 July 2016 at 22:33, Paul Sokolovsky <systems-support(a)linaro.org> >> wrote: >> >>> —Write replies above— >>> >>> I've removed stray branch in refs/for/ namespace. And as Andy mentions, >>> this is second case in last week. Please remember/remind your colleages >>> that for gerrit, dev-private-*review*.linaro.org URL should be used, >>> and using "git review" is largely preferred to directly pushing to >>> refs/for/*. >>> >>> Yongqin Liu created this request. Bero Rosenkränzer, Vishal Bhoj and >>> Satish Patel are participating. >>> You can reply directly to this email to add any further comments or >>> attachments. >>> See request details and updates for #SYS-55 >>> <https://servicedesk.linaro.org/servicedesk/customer/portal/4/SYS-55?sda_sou…> >>> - "Can not submit changes on android-patchsets.git to >>> dev-private-review.linaro.org for review" >>> ------------------------------ >>> >>> Linaro Help Center sent you this message, *powered by* JIRA Service Desk >>> <http://www.atlassian.com/software/jira/service-desk> >>> >> >> >> >> -- >> Best Regards, >> Yongqin Liu >> --------------------------------------------------------------- >> #mailing list >> linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> >> http://lists.linaro.org/mailman/listinfo/linaro-android >> >> _______________________________________________ >> linaro-android mailing list >> linaro-android(a)lists.linaro.org >> https://lists.linaro.org/mailman/listinfo/linaro-android >> >> -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

7 years, 10 months

Re: [Linaro] Comment posted to request #SYS-55: Can not submit changes on android-patchsets.git to dev-private-review.linaro.org for review

by YongQin Liu

Hi, Bero, Satish When you submit changes on android-patchsets repository to dev-private- *review*.linaro.org for review, please run *git review* to submit your changes for review, we have .gitreview file in the repository for using that command. To use "git review", git-review package needs to be installed with commands like this: *sudo apt-get install git-review* Thanks, Yongqin Liu On 1 July 2016 at 22:33, Paul Sokolovsky <systems-support(a)linaro.org> wrote: > —Write replies above— > > I've removed stray branch in refs/for/ namespace. And as Andy mentions, > this is second case in last week. Please remember/remind your colleages > that for gerrit, dev-private-*review*.linaro.org URL should be used, and > using "git review" is largely preferred to directly pushing to refs/for/*. > > Yongqin Liu created this request. Bero Rosenkränzer, Vishal Bhoj and > Satish Patel are participating. > You can reply directly to this email to add any further comments or > attachments. > See request details and updates for #SYS-55 > <https://servicedesk.linaro.org/servicedesk/customer/portal/4/SYS-55?sda_sou…> > - "Can not submit changes on android-patchsets.git to > dev-private-review.linaro.org for review" > ------------------------------ > > Linaro Help Center sent you this message, *powered by* JIRA Service Desk > <http://www.atlassian.com/software/jira/service-desk> > -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

7 years, 10 months

Two questions for Hikey AOSP

by Leo Yan

Hi John, [ + linaro-android ML ] I have two questions for working on AOSP Hikey: - When use "adb shell" to execute commands, then it will return back the execution value and error code. Usually we will get back the new line character as "\r\n", but I found for AOSP releasing it will only return back "\n" for new line. So is this decided by system's booting script or decided by shell's building? I want to change back to use "\r\n" for the format. - Second question is related with adb's permission. On my pc I need add "sudo" or change to root "sudo -s" for adb commands, otherwise it will report "insufficient permission". This is okay when I manually send adb commands, but when use python script to execute adb commands it also need add "sudo" for add adb related commands. So want to check if there have more convienent method so can let normal user to use adb command? Thanks, Leo Yan

7 years, 10 months

Re: linaro-cp jobs

by Paul Sokolovsky

Hello Ben, On Tue, 24 May 2016 15:16:26 +0100 Benjamin Copeland <ben.copeland(a)linaro.org> wrote: > linaro-cp jobs that have published in last 7 days using v2: > > https://android-build.linaro.org/jenkins/job/linaro-art-tip-build-nexus5x-M… > > https://android-build.linaro.org/jenkins/job/linaro-art-tip-build-nexus9-Mi… > > https://android-build.linaro.org/jenkins/job/linaro-art-stable-m-build-juno… > > Can they just be edited on the webui? My guess is yes. Vishal, Bero, any concerns? > > Ben -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

7 years, 11 months

[IMPORTANT] Regression after android-review.linaro.org upgrade to Gerrit 2.12.2

by Paul Sokolovsky

Hello, Summary: Your SSH username on https://android-review.linaro.org will now match Linaro username (first.last) after the next login. You local repository clones need to be updated for new username. Detailed description: https://android-review.linaro.org was the first Gerrit server in Linaro, when there were no central LDAP user database yet. As a result, there were free-form SSH usernames used, instead of the later standard first.last as used on all the other Gerrit servers. This inconsistency was a subject of background concern for Systems team, but of course not something having enough priority to "fix". However, Gerrit 2.12.2 upgrade started tonight uncovered following issue: Gerrit tries to synchronize its SSH username setting with LDAP, and fails, as Gerrits own rules disallow changing of username. The symptom of this is error "Authentication temporary unavailable" when a user with "old" SSH username tries to login via browser. While this can be classified as a Gerrit bug (and previous versions were smart enough), we'll unlikely find any timely solution to keep things as they are. So, it makes sense to take a chance of cleaning up username and making this server follow standard username conventions. Consequently: 1. All usernames which don't match "first.last" pattern are reset. 2. If you are affected, you won't be able to perform SSH operations (like git clone/push) until you login via web interface. 3. On the next login via web interface, it will be set to LDAP's "first.last" value. 4. You will need to update remotes of your existing git clones to new username (or alternatively, re-clone). 5. If you already use "first.last" SSH username, you're unaffected. The list of users affected is given below. While it seems long, majority of enrties there are for people no longer at Linaro, or for community accounts (which didn't work since we switched to LDAP anyway). If you need further assistance, please open a ticket at https://servicedesk.linaro.org/servicedesk/customer/portal/4 . Thanks, Paul username:Ng username:pfefferz username:asac username:james_w username:fgiff username:jserv username:mabac username:deeptik username:cyang username:mpoirier username:ndec username:mwaddel username:mansson username:Sachin username:vishalbhoj username:suapapa username:fabo username:pabhishek username:cnxsoft username:amitdanielk username:patrikryd username:sangwook username:ericm username:pundiramit username:glandium username:eazyigz username:tixy username:danilo username:john username:nytowl username:tony_tu username:Sangwook username:StefanEkenberg username:uichi username:plars username:zyga username:ruppi username:ebenpor username:jhkim username:Annamalai username:markoncomputer username:Claude username:tianhongwang username:rchand00 username:omarrmz username:aviksil username:nvl1109 username:a0132810 username:pelya username:krtaylor username:developer4563 username:yusufbu username:dzinman username:arussello username:mdupuy username:williamcharles username:aorth username:lanaczko username:rmcc username:kcrudup username:kelvin username:angelsl username:unixmanlinuxboy username:Quiter username:sourxsunny username:pbeeler username:anmar username:wucongdonglai username:bambi username:rperier username:sgt username:roalex username:vishveshwarbhat username:therbom username:rajagopalvenkat username:winner00 username:ramesh username:abelloni username:sparksco username:fahadkdi username:ryanharkin username:axelfagerstedt username:nocoast username:milo username:fcarpenter username:hongbozhang username:fahadk username:pelya2 username:janjic username:dpervushin username:qoowater username:cerial username:tinojantony username:stephaneeee username:kishoreboddu username:nuclearmistake username:SanjasdfsafsffaySinghsdfasfRawat username:donvigo username:tinojgit username:afarah username:mechmetal username:akbennett username:c username:sikuner username:wasungkim username:stevanr username:deqiang username:anilkumar username:willnewton username:codeart username:lrabiet username:Bintian username:bintian username:vishalbhoj2 username:tusharbehera username:jbergsag username:tgall username:amitkhare username:neo username:paramanands username:sumit username:danielt username:help username:XavierHsu username:Serban username:Z username:koenkooi (127 rows) -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

7 years, 12 months

[ANN] Gerrit 2.12.2 upgrade finished

by Paul Sokolovsky

Hello, The planned upgrade to Gerrit 2.12.2 is finished, all active Linaro servers have been upgraded. There were changes requiring action on users's side for https://android-review.linaro.org (see previous email "Regression after android-review.linaro.org upgrade to Gerrit 2.12.2"). There was second issue on https://android-review.linaro.org where a patch after clicking "Submit" was merged into the repository, but stuck in conflicting state in the web interface. This is believed to be caused by reliance on online reindexing introduced in recent Gerrit versions, which proved to be non-robust by looking at the multiple exceptions in logs. android-review.linaro.org has been reindexed in offline mode and patches verified to be processed correctly, and all following servers were upgraded in this mode. If you spot any issues, please report them via https://servicedesk.linaro.org/servicedesk/customer/portal/4 -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

8 years

[ANN] Upcoming Gerrit 2.12 upgrade

by Paul Sokolovsky

Hello, 4 months have passed since the previous Gerrit upgrade (see below for reference), when Systems team had wanted to upgrade directly to 2.12, but due to last-minute issues discovered in it, upgraded to 2.11.5 instead. Gerrit is at 2.12.2 now, with many issues fixed and it being quite stable now. We also have stakeholders waiting for 2.12 functionality any day now. So, Systems team plan to upgrade the following systems: review.linaro.org android-review.linaro.org dev-private-review.linaro.org lhg-review.linaro.org starting end of day Friday, April 29th and throughout Saturday April 30th. Let us know if you have questions or concerns (for example, if you need uninterrupted Gerrit access until end of the US day on April 29). Thanks, Paul Begin forwarded message: Date: Mon, 14 Dec 2015 19:01:46 +0200 From: Paul Sokolovsky <Paul.Sokolovsky(a)linaro.org> To: linaro-dev <linaro-dev(a)lists.linaro.org>, linaro-android <linaro-android(a)lists.linaro.org>, "systems(a)linaro.org" <systems(a)linaro.org> Subject: [ANN] Planning next Gerrit upgrade Hello, We upgraded from Gerrit 2.8 to 2.10 in the beginning of September, and it went pretty smooth and let us overcome few annoying issues and enjoy few new features and better integration with other apps. Unfortunately, 3 months later, 2.10 also feels old, with 2.12 having been released in the interim. With various Linaro groups continuing to leverage advanced Gerrit features and integrations with other apps (Jenkins, Bugzilla), Systems team faces various bugs and issues. None of these issues are too grave, but they're quite convoluted and take much time to be researched and understood. And then we find out that it's a known issue in 2.10, which was fixed in later versions. Jenkins' Gerrit integration already requires 2.12 for full functionality and warns about our version being too old and some features not supported. Which in turns brings concerns that every time it doesn't work as expected, it may be because Gerrit plugin is no longer tested with 2.10 and hits some issue pertaining to it. With that in mind, Systems team would like to start planning for next Gerrit upgrade, and move straight to the latest, 2.12. To remind, the reason we didn't upgrade to 2.11 last time, was because 2.10 was the last version which included old-style change review screen, and we wanted to provide smoother transition and let people to try the new screen at their own pace. So, if you still use the old design, please go to https://review.linaro.org/#/settings/preferences , and in "Change View:" dropdown, select "New Screen", and give it a chance with the help of this doc: https://review.linaro.org/Documentation/user-review-ui.html And if you have any concerns regarding the upgrade, please speak up now. Otherwise, we can do it in one of the following timeframes: 1. Upgrade in January. 2. Upgrade a bit later, but still before the Connect. 3. Discuss and plan upgrade at the Connect. Systems team votes for the choice 1, upgrade next month (apparently, by the end of), as that will allows us to deliver smoother Gerrit experience to other teams, instead of firefighting older version issues. Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

8 years

Fwd: sepolicy directory moved

by YongQin Liu

---------- Forwarded message ---------- From: Nick Kralevich <nnk(a)google.com> Date: 30 March 2016 at 23:58 Subject: sepolicy directory moved To: "seandroid-list(a)tycho.nsa.gov" <seandroid-list(a)tycho.nsa.gov> Hi all, If you sync AOSP, you'll find that the Android sepolicy directory has changed locations. It was moved from external/sepolicy to system/sepolicy. Having the directory in external/ was confusing to other parts of Google, since this project isn't downstream of any other project. Sorry for the breakage this caused. -- Nick -- Nick Kralevich | Android Security | nnk(a)google.com | 650.214.4037 _______________________________________________ Seandroid-list mailing list Seandroid-list(a)tycho.nsa.gov To unsubscribe, send email to Seandroid-list-leave(a)tycho.nsa.gov. To get help, send an email containing "help" to Seandroid-list-request(a)tycho.nsa.gov. -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

8 years

Re: 咨询

by YongQin Liu

Hi, kecheng So you can boot your PandaboardES with the image downloaded from http://releases.linaro.org/14.05/android/panda/, and you can use your DS-5 with it right? And your problem is that you can not find the CPU PMU data with your DS-5 tool? If so I don't think I can help you much here. I have no idea about the CPU PMU data. It might be better to check with the DS-5 team on how to collect the CPU PMU data. Just one thing I can think of is that, do you need to configure the DS-5 to collect the CPU PMU data if that is not collected by default? And I add linaro-android@ in the loop, there might be more people can help you. Thanks, Yongqin Liu On 30 March 2016 at 22:51, 季柯丞 <jkcll302089(a)gmail.com> wrote: > Dear Mr liu: > Hi, my name is Ji kecheng. I am a PhD of Southeast University. > We wanna use DS-5 to get the CPU PMU(Performance Monitor Unit) with the > Pandaboard ES(OMAP 4430/OMAP 4460). > However, we have tried the image downloaded with the link as follow, it > doesn't work. > http://releases.linaro.org/14.05/android/panda/ > > We found the gator.ko has been integrated in the image. But we cannot > fetch any PMU data. > Could you help me to fix this problem? > > Ji Kecheng > Best Regards > -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

8 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-android