All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2018.11 delayed a day
Date: Tue, 13 Nov 2018 21:36:17 +0530	[thread overview]
Message-ID: <CAMty3ZAyEcWB8_WpkQev+V1NtFjXRRkuKkeowX0zbnAEUh99og@mail.gmail.com> (raw)
In-Reply-To: <20181113155701.8C211240044@gemini.denx.de>

On Tue, Nov 13, 2018 at 9:27 PM Wolfgang Denk <wd@denx.de> wrote:
>
> Dear Jagan,
>
> In message <CAMty3ZC_u=cigEYqj+fsurU8x=pqLCQ8HbVEsrA1qVFvR3ciWQ@mail.gmail.com> you wrote:
> >
> > > That patch is buggy and needs to be respun and retested. I don't think
> > > you can push known buggy patch into a release as a fix.
> >
> > True, ie what my yesterday plan [1] but this seems to break some know
> > functionalities in MTD, can't we go with some immediate fix for this?
>
> Your request makes no sense.  You just saw what "immediate fixes"
> mean: adding untested code, which will make things not better, but
> rahter worse, as you _think_ you have fixed something - while in
> fact you have done the opposite.
>
> It is _always_ a Good Thing to allow for sufficient time for
> testing.  Even if this delays a release.

These changes were fully tested, not an immediate changes. What I mean
a immediate fix here is not for the series, for the comment mentioned
by Marek about patch 1/5.

  reply	other threads:[~2018-11-13 16:06 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 [this message]
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

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=CAMty3ZAyEcWB8_WpkQev+V1NtFjXRRkuKkeowX0zbnAEUh99og@mail.gmail.com \
    --to=jagan@amarulasolutions.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.