From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] score cleanups
Date: Mon, 29 Jun 2009 18:28:57 +0200 [thread overview]
Message-ID: <200906291828.57948.arnd@arndb.de> (raw)
In-Reply-To: <OF25C38F64.D04F8269-ON482575E4.003CD5CE-482575E4.003E9943@sunplusct.com>
On Monday 29 June 2009, liqin.chen@sunplusct.com wrote:
> Arnd Bergmann <arnd@arndb.de> 写于 2009-06-27 22:08:12:
>
> > Hi Liqin,
> >
> > I've gone over your code a bit with sparse and some clues,
> > cleaning up some areas that stuck out.
> >
> > Please check that these make sense.
>
> Hi Arnd,
>
> Code updating had finished and verified.
Ok, I've pushed out my original patches now. Unfortunately,
the way you sent back the patches was not helpful. Your mail
client still suffers from line-wrapping, which makes it impossible
to apply and you dropped all the changelog entries that I wrote.
It took me longer to split the changes into logical patches
with an appropriate changelog, so they really should not
be merged again. If you don't have a comment for the patches,
a better action would have been to reply with 'Acked-by:
Chen Liqin <liqin.chen@sunplusct.com>'.
>
> Signed-off-by: Chen Liqin <liqin.chen@sunplusct.com>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Here you mixed up the order of the 'Signed-off-by:'-lines.
If you forward a patch from someone else, you should always
put your own S-O-B after all the the others, not before them.
of(u32))) {
> @@ -151,7 +152,7 @@ int apply_relocate_add(Elf_Shdr *sechdrs, const char
> *strtab,
> /* Given an address, look for it in the module exception tables. */
> const struct exception_table_entry *search_module_dbetables(unsigned long
> addr)
This is one example of how the line wrapping broke the patch. It's basically
impossible to apply and test if the patch is broken like this.
Arnd <><
prev parent reply other threads:[~2009-06-29 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 14:08 [PATCH 0/6] score cleanups Arnd Bergmann
2009-06-27 14:08 ` [PATCH 1/6] score: add missing #includes Arnd Bergmann
2009-06-27 14:08 ` [PATCH 2/6] score: add address space annotations Arnd Bergmann
2009-06-27 14:08 ` [PATCH 3/6] score: fix function prototypes Arnd Bergmann
2009-06-27 14:08 ` [PATCH 4/6] score: cleanups: dead code, 0 as pointer, shadowed variables Arnd Bergmann
2009-06-27 14:08 ` [PATCH 5/6] score: make irq.h definitions local Arnd Bergmann
2009-06-27 14:08 ` [PATCH 6/6] score: clean up mm/init.c Arnd Bergmann
2009-06-29 11:18 ` [PATCH 0/6] score cleanups liqin.chen
2009-06-29 16:28 ` Arnd Bergmann [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=200906291828.57948.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
/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