From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Microblaze/Xilinx drivers changes
Date: Tue, 13 Sep 2011 16:40:32 +0200 [thread overview]
Message-ID: <4E6F6B60.8080205@monstr.eu> (raw)
In-Reply-To: <20110913135732.1F3A11408E93@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Michal Simek,
>
> In message <4E6F5C13.3000005@monstr.eu> you wrote:
>>> Please read:
>>> http://www.denx.de/wiki/view/U-Boot/Patches#Sending_updated_patch_versions
>> What about patch resubmit or resend?
>
> Resending unchanged patches should be avoided, if possible. First, it
> just wastes bandwith and storage space. Second (and more important),
> PatchWork has problems with this: it locates patcehs based on their
> hashes, and for reposted patches, it will always find the _oldest_
> matching patch. So even if we set N-1 of your repostings to
> "Superseded" or similar, Patchwork will set the oldest of these as
> "Accepted" and your Nth posting remains in state "New".
>
> [Only the body of the patch is relevant here, so even postings of the
> same patch by different people or with changed commit messages will be
> handled like that.]
>
>
> So only resend when you have large series of patches with very few
> unchanged patches in them.
ok. Let's look at it.
I my repo are 4 patch series.
1. emaclite: 10 patches. At least 6 will be resubmit.
http://patchwork.ozlabs.org/patch/111768/
http://patchwork.ozlabs.org/patch/111769/
http://patchwork.ozlabs.org/patch/111770/
http://patchwork.ozlabs.org/patch/111771/
Probably not possible to apply because of v2 in 111772
http://patchwork.ozlabs.org/patch/111773/
http://patchwork.ozlabs.org/patch/111775/
2. microblaze series - 4 resubmits
http://patchwork.ozlabs.org/patch/112528/
http://patchwork.ozlabs.org/patch/112529/
http://patchwork.ozlabs.org/patch/112530/ - depend on patch from emaclite series not functional - just to avoid conflict
http://patchwork.ozlabs.org/patch/112531/
+ 3 patches which I can't see on patchwork but can see it on mailing list.
3. serial multi uartlite v3 required - 1 resubmit
+ http://patchwork.ozlabs.org/patch/113567/ - wire up for MB
4. axi ethernet v3 required - 1 resubmit
+ http://patchwork.ozlabs.org/patch/112533/ - wire up for MB
Series 3 and 4 should go together because the first patch must be driver change and then MB changes.
ok. Can I delegate patches through patchwork which are not review and probably should be reviewed or applied?
Or change subjects for every patch if is new version or resend?
Regards,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2011-09-13 14:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 7:09 [U-Boot] Microblaze/Xilinx drivers changes Michal Simek
2011-09-13 7:09 ` [U-Boot] [PATCH 01/26] net: emaclite: Change driver name and add address Michal Simek
2011-09-13 7:09 ` [U-Boot] [PATCH 02/26] net: emaclite: Remove deviceid property Michal Simek
2011-09-13 7:09 ` [U-Boot] [PATCH 03/26] net: emaclite: Use calloc instead of malloc Michal Simek
2011-09-13 7:09 ` [U-Boot] [PATCH 04/26] net: emaclite: Remove baseaddress from xemaclite Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 05/26] net: emaclite: Use dynamic allocation Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 06/26] net: emaclite: Setup RX/TX ping pong for every instance Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 07/26] net: emaclite: Use unsigned long for baseaddr Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 08/26] net: emaclite: Move RX/TX ping pong initialization to board Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 09/26] net: emaclite: Use PKTSIZE directly Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 10/26] net: emaclite: Fix coding style Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 11/26] microblaze: Support CTRL+C when tftp is running Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 12/26] microblaze: Support flashes on lower addresses Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 13/26] microblaze: Initialize jumptable and console Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 14/26] microblaze: Fix unaligned.h for endians Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 15/26] microblaze: Copy bootfile from variables Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 16/26] microblaze: Remove debug saving value Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 17/26] microblaze: Setup MB vectors if feature is enable for u-boot Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 18/26] microblaze: Save and restore first unused vector Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 19/26] microblaze: Clean up reset asm code Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 20/26] microblaze: Do not select NFS for platforms without ethernet Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 21/26] microblaze: Remove address offset for uart16550 Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 22/26] microblaze: Enable FDT/FIT support Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 23/26] serial: uartlite: Support for SERIAL_MULTI Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 24/26] microblaze: Enable SERIAL_MULTI Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 25/26] net: axi_ethernet: Add driver to u-boot Michal Simek
2011-09-13 7:10 ` [U-Boot] [PATCH 26/26] microblaze: Wire up axi_ethernet driver initialization Michal Simek
2011-09-13 17:36 ` [U-Boot] [PATCH 23/26] serial: uartlite: Support for SERIAL_MULTI Mike Frysinger
2011-09-13 17:34 ` [U-Boot] [PATCH 12/26] microblaze: Support flashes on lower addresses Mike Frysinger
2011-09-14 6:48 ` Michal Simek
2011-09-13 17:33 ` [U-Boot] [PATCH 11/26] microblaze: Support CTRL+C when tftp is running Mike Frysinger
2011-09-13 17:37 ` Mike Frysinger
2011-09-14 6:51 ` Michal Simek
2011-09-13 9:53 ` [U-Boot] Microblaze/Xilinx drivers changes Wolfgang Denk
2011-09-13 11:16 ` Michal Simek
2011-09-13 13:16 ` Marek Vasut
2011-09-13 13:35 ` Michal Simek
2011-09-13 13:52 ` Marek Vasut
2011-09-13 13:57 ` Wolfgang Denk
2011-09-13 14:40 ` Michal Simek [this message]
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=4E6F6B60.8080205@monstr.eu \
--to=monstr@monstr.eu \
--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.