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 <afaer...@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 <s...@chromium.org> > >> Cc: Kever Yang <kever.y...@rock-chips.com> > >> Cc: Heiko Stübner <he...@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
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot