From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Bryan Wu <bryan.wu@analog.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm snapshot broken-out-2007-03-24-00-14.tar.gz uploaded
Date: Sat, 24 Mar 2007 07:38:33 -0800 [thread overview]
Message-ID: <20070324073833.af78ddb4.akpm@linux-foundation.org> (raw)
In-Reply-To: <46050D05.1000205@googlemail.com>
On Sat, 24 Mar 2007 12:35:33 +0100 Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
>
> akpm@linux-foundation.org napisał(a):
> > The mm snapshot broken-out-2007-03-24-00-14.tar.gz has been uploaded to
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-03-24-00-14.tar.gz
> >
> > It contains the following patches against 2.6.21-rc4:
>
> Bryan, your patch (blackfin-arch-2.6.21-rc4-mm1-update.patch) doesn't apply
> clean. I've got a lot of "1 out of 1 hunk FAILED -- rejects in file".
>
> Applying patch patches/blackfin-arch-2.6.21-rc4-mm1-update.patch
> patching file arch/blackfin/Kconfig
> patching file arch/blackfin/Makefile
> patching file arch/blackfin/kernel/Makefile
> patching file arch/blackfin/kernel/asm-offsets.c
> Hunk #1 FAILED at 6.
> 1 out of 1 hunk FAILED -- rejects in file arch/blackfin/kernel/asm-offsets.c
> patching file arch/blackfin/kernel/bfin_dma_5xx.c
That's because it contains CVS control strings. I fixed it locally,
but please don't add CVS control strings to the kernel.
next prev parent reply other threads:[~2007-03-24 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 8:16 mm snapshot broken-out-2007-03-24-00-14.tar.gz uploaded akpm
2007-03-24 11:35 ` Michal Piotrowski
2007-03-24 15:38 ` Andrew Morton [this message]
2007-03-24 11:54 ` Michal Piotrowski
2007-03-24 17:18 ` Michal Piotrowski
2007-03-24 18:16 ` Andrew Morton
2007-03-24 19:36 ` David Miller
2007-03-25 11:52 ` Michal Piotrowski
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=20070324073833.af78ddb4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.