Skip to content

ARM: kirkwood: fdt: convert kirkwood init funcs to fdt

Arnd Bergmann linux-arm-kernel linux-devicetree 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 of 4 patches 0 repliesNew

3 of 4 patches are in this archive. The cover letter announces 4.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
3/4ARM: kirkwood: convert rtc-mv to fdt.+0 -00 replies
4/4ARM: kirkwood: convert orion-wdt to fdt.+0 -01 reply
4/4ARM: kirkwood: convert orion-wdt to fdt.+0 -03 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/4] ARM: kirkwood: fdt: convert kirkwood init funcs to fdt
Quoted 21 lines · Jason
Quoted 9 lines · Arnd Bergmann
Quoted 4 lines · Jason

Thanks for the feedback. I'll redo this series and resubmit. Did you catch my patch from yesterday?

[PATCH v3] ARM: kirkwood: covert orion-spi to fdt. [1]

Yes, I saw that. It looks good and I was just waiting if other people have comments on it. Maybe you can put it into the same git tree as these ones when they are ready and you send a pull request.

Okay, I have a local branch, 'dreamplug_dt' based at v3.3-rc3. It includes the two patches you've already merged into your tree:

c9780e7 ARM: kirkwood: add dreamplug (fdt) support. dbc3c26 ARM: kirkwood: convert uart0 to devicetree.

Plus the spi/flash/partitions, and the most recent series.

Can I just do:

Quoted 7 lines

git push linux-kirkwood dreamplug_dt:kirkwood_dt

Then, issue a pull request for

git://git.infradead.org/users/jcooper/linux-kirkwood.git kirkwood_dt

and reference the first uncommitted patch?

I have other commit IDs for the two patches that I took from your emails, so you should rebase the other patches on top of the version that I have in the arm-soc/kirkwood/board branch, otherwise we end up with duplicate commits my tree when I pull them again.

Quoted 6 lines

Most of the googlings for 'pull request' yield github's "click the button", yuck.

Also, is there an equivalent to 'git format-patch/send-email' for pull requests? The pull requests I've looked at seem awfully consistent in formatting.

It's "git request-pull".

Arnd