From: Konrad Dybcio <konradybcio@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 0/5] ARM: SoC: changes for v5.9
Date: Wed, 5 Aug 2020 21:58:23 +0200 [thread overview]
Message-ID: <CAMS8qEUaFP8du8NJ098baKPqLtGG_PNu4oJjtL0dHVN-4N6xXw@mail.gmail.com> (raw)
In-Reply-To: <20200805194512.bh5hds2l46opcole@duo.ucw.cz>
> I did not know how popular PinePhone is. Does it currently have useful
> battery life?
It basically sells out in a few days after a new batch is up :D You
might want to join some pine64 irc/matrix/telegram channels.
Currently, as far as I'm aware (I haven't got one), it can survive a
full day but enhancements are still coming.
> Would something like phone@vger.kernel.org be useful for low-level
> stuff?
It would certainly make for less spam (yes, I once got (jokingly)
called out for "spamming" linux-arm-msm :D) on the general arm lists.
Many commits just tackle DTS or some bizarre only-found-on-phones
hardware. Considering Xiaomi releases 1 phone a week on average,
expect to be flooded when mainlining gets popular on sites like
XDA-Developers forums where many Android devs currently are. Also it
would be easier for people to find other phone/mobile developers.
Also, you guys might want to consider arch/arm64/boot/dts/qcom/vendor
in the future to prevent it from becoming a mess of a directory that
arch/arm/boot/dts is (though that will obviously take some time) :P
Konrad
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Dybcio <konradybcio@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
SoC Team <soc@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [GIT PULL 0/5] ARM: SoC: changes for v5.9
Date: Wed, 5 Aug 2020 21:58:23 +0200 [thread overview]
Message-ID: <CAMS8qEUaFP8du8NJ098baKPqLtGG_PNu4oJjtL0dHVN-4N6xXw@mail.gmail.com> (raw)
In-Reply-To: <20200805194512.bh5hds2l46opcole@duo.ucw.cz>
> I did not know how popular PinePhone is. Does it currently have useful
> battery life?
It basically sells out in a few days after a new batch is up :D You
might want to join some pine64 irc/matrix/telegram channels.
Currently, as far as I'm aware (I haven't got one), it can survive a
full day but enhancements are still coming.
> Would something like phone@vger.kernel.org be useful for low-level
> stuff?
It would certainly make for less spam (yes, I once got (jokingly)
called out for "spamming" linux-arm-msm :D) on the general arm lists.
Many commits just tackle DTS or some bizarre only-found-on-phones
hardware. Considering Xiaomi releases 1 phone a week on average,
expect to be flooded when mainlining gets popular on sites like
XDA-Developers forums where many Android devs currently are. Also it
would be easier for people to find other phone/mobile developers.
Also, you guys might want to consider arch/arm64/boot/dts/qcom/vendor
in the future to prevent it from becoming a mess of a directory that
arch/arm/boot/dts is (though that will obviously take some time) :P
Konrad
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-05 19:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 21:34 [GIT PULL 0/5] ARM: SoC: changes for v5.9 Arnd Bergmann
2020-08-03 21:34 ` Arnd Bergmann
2020-08-03 21:36 ` [GIT PULL 1/5] ARM: defconfig updates " Arnd Bergmann
2020-08-03 21:36 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-03 21:44 ` [GIT PULL 2/5] ARM: SoC: DT changes " Arnd Bergmann
2020-08-03 21:44 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-03 21:47 ` [GIT PULL 3/5] ARM: SoC " Arnd Bergmann
2020-08-03 21:47 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-04 7:02 ` Joel Stanley
2020-08-04 7:02 ` Joel Stanley
2020-08-04 7:33 ` Andy Shevchenko
2020-08-04 7:33 ` Andy Shevchenko
2020-08-04 7:39 ` Andy Shevchenko
2020-08-04 7:39 ` Andy Shevchenko
2020-08-04 7:55 ` Linus Walleij
2020-08-04 7:55 ` Linus Walleij
2020-08-04 18:38 ` Linus Torvalds
2020-08-04 18:38 ` Linus Torvalds
2020-08-03 21:49 ` [GIT PULL 4/5] ARM: SoC driver updates " Arnd Bergmann
2020-08-03 21:49 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-03 21:50 ` [GIT PULL 5/5] ARM: new SoC support " Arnd Bergmann
2020-08-03 21:50 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-05 17:27 ` [GIT PULL 0/5] ARM: SoC: changes " Pavel Machek
2020-08-05 17:27 ` Pavel Machek
2020-08-05 19:06 ` Arnd Bergmann
2020-08-05 19:06 ` Arnd Bergmann
2020-08-05 19:28 ` Konrad Dybcio
2020-08-05 19:28 ` Konrad Dybcio
2020-08-05 19:45 ` Pavel Machek
2020-08-05 19:45 ` Pavel Machek
2020-08-05 19:58 ` Konrad Dybcio [this message]
2020-08-05 19:58 ` Konrad Dybcio
2020-08-05 22:12 ` Konrad Dybcio
2020-08-05 22:12 ` Konrad Dybcio
2020-08-05 19:32 ` Pavel Machek
2020-08-05 19:32 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMS8qEUaFP8du8NJ098baKPqLtGG_PNu4oJjtL0dHVN-4N6xXw@mail.gmail.com \
--to=konradybcio@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=soc@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.