[U-Boot] [PATCH v4 0/4] Add basic clock and pinmux functions to the Tegra2

[Albert ARIBAUD <albert.u.boot@aribaud.net>]

Le 30/08/2011 18:23, Simon Glass a ?crit :
> This patch series adds basic clock and pinmux functions to the Tegra2, and
> modifies the ap20 and board code to use them.
>
> Changes in v2:
> - Removed use of bitfield access macros
> - Now uses manual shifts and masks
>
> Changes in v3:
> - Removed bitfield shift/mask macros and write these out manually
> - Rebased to take account to new MMC patches
> - Remove future time function
> - No microsecond timing changes as I am unsure of the state of this in U-Boot
>
> Changes in v4:
> - Rebase against U-Boot master
> - Remove future time function from header also
>
> Simon Glass (4):
>    Tegra2: Add microsecond timer function
>    Tegra2: Add more clock support
>    Tegra2: Add additional pin multiplexing features
>    Tegra2: Use clock and pinmux functions to simplify code

Patch series applied to u-boot-arm/master, with manual fix of three 
empty lines at EOF in patches 1 through 3.

These empty lines and other whitespace errors can be found and fixed by 
the submitter before sending the patch to the list: just apply the 
patches to a local branch created at the intended commit where 
application will happen, i.e.:

	git fetch u-boot
or
	git fetch u-boot-arm

(assuming you have a remote nicknamed u-boot[-arm])

	git checkout u-boot/master -b temp
or
	git checkout u-boot-arm/master -b temp

	git am 0001-xxxxx
	git am 0002-xxxxx
(etc)

If any empty line or bad whitespace warning occurs, go back to your 
working branch, fix and regenerate the patch set, then go back to temp 
and reset it:

	git checkout temp

	git reset --hard u-boot/master
or
	git reset u-boot-arm/master

Then you can run the

	git am 0001-xxxxx
	...

again.

When the patches are sent, you can go back to your working branch and 
then do a

	git branch -D temp

to remove the temporary branch.

Amicalement,
-- 
Albert.