From: Paul Mackerras <paulus@samba.org>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/15] qe_lib: Add common files
Date: Mon, 2 Oct 2006 17:37:20 +1000 [thread overview]
Message-ID: <17696.49584.252608.249426@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20060930183333.0ec7fe0f.kim.phillips@freescale.com>
Kim Phillips writes:
> qe_lib: Add common files
> diff --git a/arch/powerpc/sysdev/qe_lib/Makefile b/arch/powerpc/sysdev/qe_lib/Makefile
> new file mode 100644
> index 0000000..9a54a81
> --- /dev/null
> +++ b/arch/powerpc/sysdev/qe_lib/Makefile
> @@ -0,0 +1,8 @@
> +#
> +# Makefile for the linux ppc-specific parts of QE
> +#
> +obj-$(CONFIG_QUICC_ENGINE)+= qe_common.o qe.o qe_ic.o qe_io.o
But qe.c, qe_ic.c and qe_io.c don't exist as of this patch, so the
kernel won't build.
Also I notice that qe_common.c gets added by this patch and then
modified by subsequent patches. Why don't we just add the final
version instead?
It looks to me like most of this series needs to be committed as one
commit so that git bisect still works. Please re-send the patches
(except the rheap fix) as a series where the kernel will build and run
after each patch in the series.
Also, when you are sending on a patch that someone else created,
please make the first non-blank line of the message say "From: "
followed by the author's name and email address, so we get the
attribution right in the git repository.
Paul.
prev parent reply other threads:[~2006-10-02 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 23:33 [PATCH 3/15] qe_lib: Add common files Kim Phillips
2006-10-02 7:37 ` Paul Mackerras [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=17696.49584.252608.249426@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=kim.phillips@freescale.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).