From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] debug macro changes for 2.6.36
Date: Sat, 31 Jul 2010 10:28:38 +0100 [thread overview]
Message-ID: <20100731092838.GE23886@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1007302138380.30558@xanadu.home>
On Fri, Jul 30, 2010 at 09:46:16PM -0400, Nicolas Pitre wrote:
> On Fri, 30 Jul 2010, Russell King - ARM Linux wrote:
> > My intention was to have your patch merged - as patches - into an
> > appropriate place in my tree, and then just before the merge window
> > run that script to remove all the references to phys_io/io_pg_offst,
> > and finally, some time later, the members from the structure.
>
> Just to be clear, would you prefer for Jeremy to send you those initial
> patches through your patch system or via a Git pull request?
I think patches would be better, so there's no dependencies on stuff I
have in my tree already - and I'll be free to add them at the most
appropriate point.
However, it seems one of the patches still contains questions over OMAP
which haven't been addressed (or maybe they have and the commit comment
hasn't been updated.) That needs resolving before they can be merged.
I've forwarded the email to linux-omap and Tony, but I'm not expecting
a reply before Monday or so as OMAP folk seem to keep to sane working
hours.
next prev parent reply other threads:[~2010-07-31 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 4:58 [GIT PULL] debug macro changes for 2.6.36 Jeremy Kerr
2010-07-30 7:18 ` Russell King - ARM Linux
2010-07-30 7:23 ` Jeremy Kerr
2010-07-30 8:14 ` Russell King - ARM Linux
2010-07-30 9:00 ` Jeremy Kerr
2010-07-31 1:46 ` Nicolas Pitre
2010-07-31 9:28 ` Russell King - ARM Linux [this message]
2010-08-03 9:40 ` Tony Lindgren
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=20100731092838.GE23886@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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