From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Request for Kirkwood new Marvell MMC Driver mainline
Date: Thu, 20 Sep 2012 23:17:59 +0200 [thread overview]
Message-ID: <505B8807.8020208@googlemail.com> (raw)
In-Reply-To: <505B5195.7080709@doukki.net>
Dear DrEagle,
On 20.09.12 19:25, DrEagle wrote:
> 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.
sounds great.
> 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
But all these changes are split into atomic patches, aren't they?
> Is there any guide to help for making cumulative patch, and for using
> git diff to make some local branch ?
Well, read http://www.denx.de/wiki/U-Boot/Patches and if I got your
question right you should read http://git-scm.com/book first.
> 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 ?
Read http://www.denx.de/wiki/U-Boot/Patches
Best regards
Andreas Bie?mann
prev parent reply other threads:[~2012-09-20 21:17 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 ` [U-Boot] Request for Kirkwood new Marvell MMC Driver mainline DrEagle
2012-09-20 21:17 ` Andreas Bießmann [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=505B8807.8020208@googlemail.com \
--to=andreas.devel@googlemail.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 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.