linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Valdis.Kletnieks@vt.edu
Cc: "Wang, Yalin" <Yalin.Wang@sonymobile.com>,
	"'Catalin Marinas'" <catalin.marinas@arm.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Will Deacon <Will.Deacon@arm.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-arm-kernel@lists.infradead.org'" 
	<linux-arm-kernel@lists.infradead.org>,
	"'linux-mm@kvack.org'" <linux-mm@kvack.org>,
	"'linux-arm-msm@vger.kernel.org'" <linux-arm-msm@vger.kernel.org>,
	DL-WW-ContributionOfficers-Linux 
	<DL-WW-ContributionOfficers-Linux@sonymobile.com>
Subject: Re: [PATCH resend] arm:extend the reserved memory for initrd to be page aligned
Date: Tue, 30 Sep 2014 09:02:09 +0200	[thread overview]
Message-ID: <20140930070209.GG31554@pengutronix.de> (raw)
In-Reply-To: <15815.1412018518@turing-police.cc.vt.edu>

Hello,

On Mon, Sep 29, 2014 at 03:21:58PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 26 Sep 2014 10:40:54 +0800, "Wang, Yalin" said:
> 
> > 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
> 
> 'diff -urN' has the advantage that it will work against a tree extracted
> from a release tarball, and doesn't have a requirement that you have git
That's wrong, patches generated by git-format-patch are also applicable
just fine on top of an extracted tar ball by patch(1).

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2014-09-30  7:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19  7:09 [PATCH resend] arm:extend the reserved memory for initrd to be page aligned Wang, Yalin
2014-09-19 10:00 ` Catalin Marinas
2014-09-25 14:31   ` Russell King - ARM Linux
2014-09-25 15:44     ` Catalin Marinas
2014-09-26  2:40       ` Wang, Yalin
2014-09-29 19:21         ` Valdis.Kletnieks
2014-09-30  7:02           ` Uwe Kleine-König [this message]
2014-09-30  9:24             ` Valdis.Kletnieks
2014-09-30  9:59           ` Russell King - ARM Linux
2014-09-28  1:50       ` Wang, Yalin
2014-09-26  1:56     ` Wang, Yalin
2014-10-08 11:54 ` Geert Uytterhoeven
2014-10-09  7:25   ` Wang, Yalin

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=20140930070209.GG31554@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=DL-WW-ContributionOfficers-Linux@sonymobile.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=Will.Deacon@arm.com \
    --cc=Yalin.Wang@sonymobile.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@arm.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).