All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Discussion topics / issues
Date: Thu, 9 Oct 2014 18:15:14 +0200	[thread overview]
Message-ID: <201410091815.14531.marex@denx.de> (raw)
In-Reply-To: <CAD6G_RSH2yLyHp80o6CTgwTO0r46d+tpcz6KndL3e+FPDmUQEQ@mail.gmail.com>

On Thursday, October 09, 2014 at 06:11:37 PM, Jagan Teki wrote:

[...]

> >> These are the qspi stuff from freescale, and I didn't understand why
> >> these goes into
> >> u-boot-arm/master. And there is no intimation of mine as well.
> > 
> > Did you comment on them at all please ? While I disagree with them
> > bypassing your tree, I see they were rotting on the ML for a month and
> > then Albert then picked those.
> 
> This is not a question of commenting - but - about the process.
> 
> Yes, I asked the author to test the changes later for a while this got
> pushed. I never thought this could happen so suddenly without any ping or
> something.
> 
> I guess some times it happens few of the patches will rotted for a while on
> ML due to some delays, but taking them with/out any ping causes over head
> if the respective owner will look at the code for later modifications.

I agree with you that there is a problem where custodians get bypassed and
that such a thing happened to me as well. This is sporadic, but apparently
annoying enough, so this should be added.

> >> Issue is that the driver itself is not in a proper shape, why does
> >> subsystem patches were
> >> pushed without the the review tag from a respective custodians.
> > 
> > I produced a hypothesis above.
> > 
> > Can you retroactively comment on them and ask the author to fix the code?
> 
> Yes - I asked the author for fixing those for few of the patches
> against that change.

Thanks!

> >> Please try to discuss this point as well "Each subsystem patch(es)
> >> should be pushed
> >> if and only if the respective custodian should marked the review tag"
> > 
> > I agree we have an issue here, but I would suggest we move this
> > discussion into a separate thread now. The subject of the email does not
> > match the topic of the thread by far.
> 
> Agreed - I mentioned this on this tread only for listing item on
> meeting, that it.

Will you join us as well? (sorry, I lost track of who will and who won't)

Best regards,
Marek Vasut

  reply	other threads:[~2014-10-09 16:15 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 12:45 [U-Boot] [SoCFPGA] next steps Marek Vasut
2014-10-08  8:58 ` Michal Simek
2014-10-08 10:39   ` Marek Vasut
2014-10-08 11:17   ` Pavel Machek
2014-10-08 20:09   ` Tom Rini
2014-10-09  8:37     ` Michal Simek
2014-10-09 11:20       ` Jagan Teki
2014-10-09 13:42         ` Marek Vasut
2014-10-09 16:11           ` Jagan Teki
2014-10-09 16:15             ` Marek Vasut [this message]
2014-10-09 16:41               ` [U-Boot] Discussion topics / issues Jagan Teki
2014-10-09 14:03       ` Marek Vasut
2014-10-09 14:45         ` Michal Simek
2014-10-09 15:57           ` Tom Rini
2014-10-09 16:10             ` Marek Vasut
2014-10-09 16:25               ` Tom Rini
2014-10-09 16:29                 ` Marek Vasut
2014-10-09 22:11         ` Pavel Machek
2014-10-09 22:24           ` Wolfgang Denk
2014-10-09 23:00             ` Pavel Machek
2014-10-10 12:22               ` Wolfgang Denk
2014-10-10 14:04                 ` Jeroen Hofstee
2014-10-10 14:26                   ` Marek Vasut
2014-10-10 14:35                     ` Fabio Estevam
2014-10-10 16:09                     ` Jeroen Hofstee
2014-10-10 19:51                       ` Albert ARIBAUD
2014-10-10 20:40                         ` Jeroen Hofstee
2014-10-10 21:13                           ` Albert ARIBAUD
2014-10-11 15:03                           ` Wolfgang Denk
2014-10-11 15:16                             ` Wolfgang Denk
2014-10-15  8:40                             ` [U-Boot] puts() and newlines (was Re: Discussion topics / issues) Pavel Machek
2014-10-15  9:42                               ` Pavel Machek
2014-10-20 15:51                               ` Tom Rini
2014-10-11 14:44                   ` [U-Boot] Discussion topics / issues Wolfgang Denk
2014-10-12 15:06                   ` Jeroen Hofstee
2014-10-09 23:05             ` Pavel Machek
2014-10-10 11:05               ` Albert ARIBAUD
2014-10-10 12:34               ` Wolfgang Denk
2014-10-10  0:12           ` Tom Rini
2014-10-08 13:18 ` [U-Boot] [SoCFPGA] next steps Dinh Nguyen
2014-10-08 19:05   ` Marek Vasut
2014-10-11 18:22 ` Masahiro YAMADA
2014-10-19 21:19   ` 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=201410091815.14531.marex@denx.de \
    --to=marex@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 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.