All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2018.11 delayed a day
Date: Wed, 14 Nov 2018 12:54:11 +0100	[thread overview]
Message-ID: <40ca45cd-6c90-387a-30bb-22a259f88828@gmail.com> (raw)
In-Reply-To: <20181114123235.215d876e@crub>

On 11/14/2018 12:32 PM, Anatolij Gustschin wrote:
> On Mon, 12 Nov 2018 23:13:29 +0100
> Marek Vasut marek.vasut at gmail.com wrote:
> 
>> On 11/12/2018 10:40 PM, Tom Rini wrote:
>>> Hey all,
>>>
>>> Since Jagan promise a v2 SPI PR for some build fixes that we should have
>>> in the release and I believe didn't get them out before the end of his
>>> day, I'm letting everyone know now to expect the release tomorrow
>>> instead, thanks!  
>>
>> Will anyone have any chance to test those fixes to verify they didn't
>> break anything ?
>>
>> I believe this is yet another manifestation of the problems of the 2
>> month release cycle, which I think is too short and stressful.
> 
> Yes, and patches with fixes sometimes wait long time without review
> or testing and miss the release, then people start to complain when
> the released code is buggy. What about this [1] patch? Could someone
> please review/test it? Can it be applied to v2018.11 ?
> 
> [1] https://patchwork.ozlabs.org/patch/985919

Yes, that's obviously a correct fix.

-- 
Best regards,
Marek Vasut

      parent reply	other threads:[~2018-11-14 11:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12 21:40 [U-Boot] [ANN] U-Boot v2018.11 delayed a day Tom Rini
2018-11-12 22:13 ` Marek Vasut
2018-11-12 22:25   ` Tom Rini
2018-11-13  0:03     ` Marek Vasut
2018-11-13  1:12       ` Tom Rini
2018-11-13  2:12         ` Marek Vasut
2018-11-13 10:33           ` Miquel Raynal
2018-11-13 10:41             ` Marek Vasut
2018-11-13 10:54               ` Boris Brezillon
2018-11-13 11:02                 ` Marek Vasut
2018-11-13 11:15                   ` Jagan Teki
2018-11-13 11:23                     ` Marek Vasut
2018-11-13 11:32                       ` Jagan Teki
2018-11-13 15:57                         ` Wolfgang Denk
2018-11-13 16:06                           ` Jagan Teki
2018-11-14  9:23                             ` Wolfgang Denk
2018-11-14  9:50                               ` Jagan Teki
2018-11-14  9:47                             ` Boris Brezillon
2018-11-14 10:21                               ` Wolfgang Denk
2018-11-13 13:30         ` Philipp Tomsich
2018-11-13 11:01       ` Stefano Babic
2018-11-14 11:32   ` Anatolij Gustschin
2018-11-14 11:40     ` Stefan Roese
2018-11-14 12:21       ` Tom Rini
2018-11-14 11:54     ` Marek Vasut [this message]

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=40ca45cd-6c90-387a-30bb-22a259f88828@gmail.com \
    --to=marek.vasut@gmail.com \
    --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 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.