[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35FD53F367049845BC99AC72306C23D103D6DB49163B@CNBJMBX05.corpusers.net>
Date: Fri, 26 Sep 2014 10:40:54 +0800
From: "Wang, Yalin" <Yalin.Wang@...ymobile.com>
To: 'Catalin Marinas' <catalin.marinas@....com>,
Russell King - ARM Linux <linux@....linux.org.uk>
CC: Will Deacon <Will.Deacon@....com>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"'linux-arm-kernel@...ts.infradead.org'"
<linux-arm-kernel@...ts.infradead.org>,
"'linux-mm@...ck.org'" <linux-mm@...ck.org>,
"'linux-arm-msm@...r.kernel.org'" <linux-arm-msm@...r.kernel.org>,
'Uwe Kleine-König'
<u.kleine-koenig@...gutronix.de>,
DL-WW-ContributionOfficers-Linux
<DL-WW-ContributionOfficers-Linux@...ymobile.com>
Subject: RE: [PATCH resend] arm:extend the reserved memory for initrd to be
page aligned
> They were so close ;)
>
> I can see three patches but none of them exactly right:
>
> 8157/1 - wrong diff format
> 8159/1 - correct format, does not have my ack (you can take this one if
> you want)
> 8162/1 - got my ack this time but with the wrong diff format again
>
> Maybe a pull request is a better idea.
>
I am really confused,
I read this web:
http://www.arm.linux.org.uk/developer/patches/info.php
it said use diff -urN to generate patch like this:
diff -Nru linux.orig/lib/string.c linux/lib/string.c
but I see other developers use git format-patch to generate patch and
submit to the patch system.
Git format-patch format can also be accepted by the patch system correctly ?
If yes, I think this web should update,
Use git format-patch to generate patch is more convenient than use diff -urN
Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists