From: Andrew Morton <akpm@osdl.org>
To: jayalk@intworks.biz
Cc: adaplas@pol.net, linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [RFC/PATCH 2.6.12-rc5 1/1] Framebuffer driver for Arc LCD board
Date: Mon, 6 Jun 2005 14:43:52 -0700 [thread overview]
Message-ID: <20050606144352.140cfe42.akpm@osdl.org> (raw)
In-Reply-To: <200506061416.j56EG18b017582@intworks.biz>
jayalk@intworks.biz wrote:
>
> I did this diff against
> rc5. Should I be doing it against -mm instead?
I generally prefer diffs against whatever is in -mm, mainly so we can see
what changed, and so that we can make sure that everyones fixups didn't get
lost.
If a patch has only been in -mm for a short period then a wholesale
replacement is OK. It gets a bit complex because people do insist on trying
to add lots of trailing whitespace to the tree and I do insist on thwarting
them, but I fix all that up.
In this case I got anal and turned your new patch into an incremental one ;)
prev parent reply other threads:[~2005-06-06 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 14:16 jayalk
2005-06-06 19:00 ` [Linux-fbdev-devel] " James Simmons
2005-06-06 21:43 ` Andrew Morton [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=20050606144352.140cfe42.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adaplas@pol.net \
--cc=jayalk@intworks.biz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®