From: jassisinghbrar@gmail.com (Jassi Brar)
To: linux-arm-kernel@lists.infradead.org
Subject: RMK closing tree to patches *this* weekend
Date: Fri, 14 May 2010 23:21:49 +0900 [thread overview]
Message-ID: <AANLkTincGbDle7n-VhWQVMOMTFqRzV4Cfh9yTKokPViQ@mail.gmail.com> (raw)
In-Reply-To: <20100514092435.GD10339@n2100.arm.linux.org.uk>
On Fri, May 14, 2010 at 6:24 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Fri, May 14, 2010 at 09:58:01AM +0900, Jassi Brar wrote:
>> On Fri, May 14, 2010 at 8:02 AM, Russell King - ARM Linux
>> <linux@arm.linux.org.uk> wrote:
>> > As of the end of this coming weekend, I'll stop taking patches for the
>> > next merge window. ?I want to tidy up the lose ends which need sorting
>> > out and give it a decent outing in linux-next for about a week before
>> > the merge window opens.
>> >
>> > So if there's any patches I've missed, please follow up to this email.
>> Hi Russell,
>>
>> Would it be possible for you to merge the PL330 core driver in your tree?
>> If so, I would make sure the platform specific stuff get up via Ben Dooks'
>> tree in time.
>
> I looked at doing that, but it conflicts in arch/arm/common/Kconfig:
>
> patching file arch/arm/common/Kconfig
> Hunk #1 FAILED at 40.
> 1 out of 1 hunk FAILED -- saving rejects to file arch/arm/common/Kconfig.rej
>
> I think this is another place where having things sorted alphabetically
> would help, rather than appending things to the end. ?That said, because
> of the changes in the versatile branch, its going to cause merge conflicts
> (which are easier to deal with than a patch which won't apply.)
>
> Could you move the PL330 option to between ICST307 and SA1111 please?
I just moved Kconfig and Makefile entries for that and submitted again
as [6132/1]
thanks
next prev parent reply other threads:[~2010-05-14 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 23:02 RMK closing tree to patches *this* weekend Russell King - ARM Linux
2010-05-14 0:35 ` Ben Dooks
2010-05-14 9:20 ` Russell King - ARM Linux
2010-05-14 0:58 ` Jassi Brar
2010-05-14 9:24 ` Russell King - ARM Linux
2010-05-14 14:21 ` Jassi Brar [this message]
2010-05-14 2:09 ` Ming Lei
2010-05-14 9:27 ` Russell King - ARM Linux
2010-05-17 9:03 ` Russell King - ARM Linux
2010-05-17 13:04 ` Nicolas Pitre
2010-05-17 13:08 ` Russell King - ARM Linux
2010-05-17 15:10 ` Russell King - ARM Linux
2010-05-17 15:44 ` Will Deacon
2010-05-17 16:18 ` Russell King - ARM Linux
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=AANLkTincGbDle7n-VhWQVMOMTFqRzV4Cfh9yTKokPViQ@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).