public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] rockchip: Initial RK3368 and GeekBox support
Date: Sun, 7 Aug 2016 09:31:56 -0400	[thread overview]
Message-ID: <20160807133156.GL9942@bill-the-cat> (raw)
In-Reply-To: <14672ec5-d381-74e8-d693-96e821b80aad@suse.de>

On Sat, Aug 06, 2016 at 06:05:29PM +0200, Andreas F?rber wrote:
> Hi Simon,
> 
> Am 06.08.2016 um 06:30 schrieb Simon Glass:
> > Hi Andreas,
> > 
> > On 17 July 2016 at 19:06, Andreas F?rber <afaerber@suse.de> wrote:
> >> Hi,
> >>
> >> This series adds initial support for RK3368 SoC and GeekBox.
> >> For more details see the commit message.
> >>
> >> Will need to be rebased onto Heiko's cleanups and Kever's RK3399 series.
> >>
> >> Regards,
> >> Andreas
> >>
> >> Cc: Simon Glass <sjg@chromium.org>
> >> Cc: Kever Yang <kever.yang@rock-chips.com>
> >> Cc: Heiko St?bner <heiko@sntech.de>
> >>
> >> Andreas F?rber (2):
> >>   dts: Import rk3368-geekbox.dts
> >>   ARM64: rockchip: Add initial support for RK3368 based GeekBox
> >>
> > 
> > Are you planning to respin these patches?
> 
> Eventually...?
> 
> > I'd like to get them applied soon.
> 
> And I'd like to get my work recognized! However, despite our previous
> IRC chat, I had to find out _while_ replying to the rk3399 mails that
> you had once again not just applied all patches (twenty minutes after
> ack'ing them on a Saturday) but already sent a pull on Tuesday my
> nighttime that I was not CC'ed on and that Tom has merged the night
> after. So it feels like I'm wasting my time here and consequently I
> stopped my review and rebase.

In the U-Boot community, we are not in the habit of cc'ing everyone with
a change in a given pull request.  Is there a tool the kernel folks use
here that makes this easy?

And the rule of thumb that I use, and I try and get everyone else to use
as well is that a patch should be out for a week before it gets picked
up and merged as that should give everyone time to review, comment and
test.  Did that not happen with the patches Simon picked up?

Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160807/667e159b/attachment.sig>

  parent reply	other threads:[~2016-08-07 13:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  1:06 [U-Boot] [PATCH 0/2] rockchip: Initial RK3368 and GeekBox support Andreas Färber
2016-07-18  1:06 ` [U-Boot] [PATCH 1/2] dts: Import rk3368-geekbox.dts Andreas Färber
2016-07-18 11:56   ` Simon Glass
2016-07-18  1:06 ` [U-Boot] [PATCH 2/2] ARM64: rockchip: Add initial support for RK3368 based GeekBox Andreas Färber
2016-07-18  1:22   ` Andreas Färber
2016-07-18 11:56   ` Simon Glass
2016-07-18 12:13   ` Heiko Stübner
2016-07-23  2:31     ` Simon Glass
2016-07-25 14:46       ` Andreas Färber
2016-08-06  4:30 ` [U-Boot] [PATCH 0/2] rockchip: Initial RK3368 and GeekBox support Simon Glass
2016-08-06 16:05   ` Andreas Färber
2016-08-06 18:52     ` Simon Glass
2016-08-07 13:31     ` Tom Rini [this message]
2016-08-07 16:46       ` Andreas Färber
2016-08-07 20:07         ` Tom Rini
2016-08-08 21:44           ` Simon Glass
2016-08-29  7:17 ` Peter Robinson

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=20160807133156.GL9942@bill-the-cat \
    --to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox