All of lore.kernel.org
 help / color / mirror / Atom feed
From: DrEagle <dreagle@doukki.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Request for Kirkwood new Marvell MMC Driver mainline
Date: Thu, 20 Sep 2012 19:25:41 +0200	[thread overview]
Message-ID: <505B5195.7080709@doukki.net> (raw)
In-Reply-To: <505B1CE4.2020709@doukki.net>

I have a patch for the support of a generic MMC driver for kirkwood Soc.
I want to make some few more fix to have sheevaplugs been updated also.

Here is the complete changelog of my patch :
- Add Marvell SDIO/MMC driver for Kirkwood SoC
- Add SDIO/MMC support for Sheevaplug board
- Fix env address for Sheevaplug board
- Fix mtdparts for Sheevaplug board
- Fix mtdids for Sheevaplug board
- Add default mtdparts for Sheevaplug board
- Add default mtdids for Sheevaplug board
- Add SATA support for Sheevaplug board

Is there any guide to help for making cumulative patch, and for using
git diff to make some local branch ?

I need, I suppose, to make patch for each subject and segment my diff
into few proposal ?
- MMC Driver
- MMC support
- Fix env
...

Is there any guide for proposing patch to be mainline supported into uboot ?

Thanks in advance for the tips,

Amicalement,


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120920/dfa02aa4/attachment.pgp>

       reply	other threads:[~2012-09-20 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <505B1CE4.2020709@doukki.net>
2012-09-20 17:25 ` DrEagle [this message]
2012-09-20 21:17   ` [U-Boot] Request for Kirkwood new Marvell MMC Driver mainline Andreas Bießmann

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=505B5195.7080709@doukki.net \
    --to=dreagle@doukki.net \
    --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.