Make Buildroot for Zedboard independent on Xilinx tools
Get series with b4
b4 am 20150704015240.662c8a78@jvnVersions newest first · linked by author and title
- v3 Latest posting 3/30 of 2 patches 0 repliesNew
- v3 posting 2/30 of 2 patches 0 repliesSuperseded
- v3 posting 1/32 patches 0 repliesSuperseded
Earlier versions · 2
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 | 2 patches | 0 replies | Superseded | |
| v1 | 0 of 2 patches | 0 replies | Superseded |
Patches in v3 posting 3/3 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [Buildroot] [PATCH v3 0/2] Make Buildroot for Zedboard independent on Xilinx tools
Hello Yann,
I see your point. I was just uncertain whether it was forgotten or if there is some issue I did not see. Now, I see you are doing very well, apologize. Recently, I've beated the contribution process (not as easy as it looks like when just passively watching the mailing list), probably I will beat also the review process after some time.
Regards
Jan
Quoted 32 lines · On Fri, 3 Jul 2015 19:40:05 +0200 "Yann E. MORIN" <[email protected]>…
Jan, All,
On 2015-07-02 14:40 +0200, Jan Viktorin spake thusly:
Quoted 1 line
will be the proposed patchs applied in the near future?
Well, we need to review and test them...
We currently have 401 patches pending in our patch queue:
https://patchwork.ozlabs.org/project/buildroot/list/Since there's not many of us doing reviews/tests, it takes time.
If you want to increase the likelyhood your patches are reviewed soon (and I've already started), you can help reduce the patch queue:
- get a patch (not yours), apply it to your Buildroot tree, build a configuration with that patch and test it (as much as you can, at least build-test in various target configurations: arm, mips... LE/BE, glibc/uClibc/musl, internal/external toolchain...) and
report your findings to the list- get a patch (not yours), look at it, and see if it fits in the Buildroot 'spirit' (code style, mandatory information,
licensing...) and report to hte list.See:
http://buildroot.net/downloads/manual/manual.html#_contributing_to_buildroot
http://buildroot.net/downloads/manual/manual.html#_reviewing_and_testing_patchesRegards,
Yann E. MORIN.