From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-staging
Date: Mon, 22 Oct 2018 20:39:44 +0200 [thread overview]
Message-ID: <20181022203944.418eed6f@crub> (raw)
In-Reply-To: <44384dba-25a8-74ed-281a-7ca267d95346@openedev.com>
Hi Jagan,
On Mon, 22 Oct 2018 23:56:14 +0530
Jagan Teki jagan at openedev.com wrote:
>On 21/10/18 1:50 AM, Anatolij Gustschin wrote:
>> On Sat, 20 Oct 2018 15:43:48 -0400
>> Tom Rini trini at konsulko.com wrote:
>> ...
>>> These all look like things that should go via the sunxi tree, and Jagan
>>> is fairly active. I'm curious, why did you pick these up presently?
>>
>> I got this series on Tuesday and then also got Acked-by and Tested-by
>> stating that is fixes LCD backlight issues on pinebook. Jagan didn't
>> respond yet, so I intervened. I'm fine if Jagan takes them via sunxi tree.
>
>Not good, patches in ML in 5 days back. better wait or ping on the
>series. I do understand these fixes will go and I saw them as well.
>Waiting for some issues to fix so all will pack all once.
I think patches fixing errors should be applied as soon as possible,
especially when these patches were tested by someone and when it is
confirmed that these fix real issues. I've lost more than tree days
recently debugging issues and it turned out that the patches for
issues I was faced were already submitted to the list, but nobody
cared to merge them.
Thanks,
Anatolij
next prev parent reply other threads:[~2018-10-22 18:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 19:35 [U-Boot] Pull request: u-boot-staging Anatolij Gustschin
2018-10-20 19:43 ` Tom Rini
2018-10-20 20:20 ` Anatolij Gustschin
2018-10-22 18:26 ` Jagan Teki
2018-10-22 18:39 ` Anatolij Gustschin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-10 11:26 Anatolij Gustschin
2019-06-10 13:42 ` Tom Rini
2019-06-10 13:50 ` Anatolij Gustschin
2018-08-11 17:15 Anatolij Gustschin
2018-08-13 0:21 ` Tom Rini
2018-08-07 6:56 Anatolij Gustschin
2018-08-07 15:32 ` Tom Rini
2016-02-06 18:18 Anatolij Gustschin
2016-02-08 20:45 ` Tom Rini
2014-10-31 0:02 Anatolij Gustschin
2014-11-04 20:00 ` Tom Rini
2014-08-21 17:17 Anatolij Gustschin
2014-08-25 12:35 ` Tom Rini
2013-03-29 13:26 Anatolij Gustschin
2013-04-01 16:30 ` Tom Rini
2013-01-14 22:28 Anatolij Gustschin
2013-01-14 22:40 ` Tom Rini
2012-11-14 13:52 Anatolij Gustschin
2012-11-19 19:59 ` Tom Rini
2012-11-08 12:39 Anatolij Gustschin
2012-11-08 15:07 ` Tom Rini
2012-10-05 23:06 Anatolij Gustschin
2012-10-08 16:09 ` Tom Rini
2012-09-21 23:10 Anatolij Gustschin
2012-09-22 0:21 ` Tom Rini
2012-09-22 0:22 ` Tom Rini
2012-09-01 12:44 Anatolij Gustschin
2012-09-01 22:46 ` Wolfgang Denk
2012-04-30 15:03 Anatolij Gustschin
2012-04-30 16:21 ` Wolfgang Denk
2012-04-16 16:42 Anatolij Gustschin
2012-04-16 21:00 ` Wolfgang Denk
2012-03-30 17:24 Anatolij Gustschin
2012-03-30 19:06 ` Wolfgang Denk
2011-12-20 21:35 Anatolij Gustschin
2011-12-20 22:15 ` Wolfgang Denk
2011-12-12 13:41 Anatolij Gustschin
2011-12-12 13:51 ` Wolfgang Denk
2011-12-09 16:36 Anatolij Gustschin
2011-12-10 21:46 ` Wolfgang Denk
2011-12-05 22:30 Anatolij Gustschin
2011-12-05 22:34 ` Wolfgang Denk
2011-11-27 19:28 Anatolij Gustschin
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=20181022203944.418eed6f@crub \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox