From: Tony Lindgren <tony@atomide.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] omap updates for 2.6.40
Date: Thu, 26 May 2011 05:55:29 -0700 [thread overview]
Message-ID: <20110526125529.GC11352@atomide.com> (raw)
In-Reply-To: <4DDE4D04.5070404@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [110526 05:48]:
> On 05/26/11 15:24, Tony Lindgren wrote:
>
> > * Igor Grinberg <grinberg@compulab.co.il> [110526 05:10]:
> >> What about this one: [PATCH v2] arm: omap2plus: move NAND_BLOCK_SIZE out of boards
> >>
> >> Why not include it? It is no new code, just generalize stuff and 11 lines off... not much but still.
> > Sorry I must have missed it.. Let's see if we can queue it
> > during the merge window as it's a trivial patch removing
> > duplicate defines.
>
> I'm failing to understand what do you mean by that...
> According to Linus ("probably Sunday - I'll be on airplanes next Monday"),
> the merge window will be closed soon.
>
> Do you mean, you will send an updated pull request?
Sorry I meant during the -rc cycle, I guess we're out of
time for the merge window to make changes.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap updates for 2.6.40
Date: Thu, 26 May 2011 05:55:29 -0700 [thread overview]
Message-ID: <20110526125529.GC11352@atomide.com> (raw)
In-Reply-To: <4DDE4D04.5070404@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [110526 05:48]:
> On 05/26/11 15:24, Tony Lindgren wrote:
>
> > * Igor Grinberg <grinberg@compulab.co.il> [110526 05:10]:
> >> What about this one: [PATCH v2] arm: omap2plus: move NAND_BLOCK_SIZE out of boards
> >>
> >> Why not include it? It is no new code, just generalize stuff and 11 lines off... not much but still.
> > Sorry I must have missed it.. Let's see if we can queue it
> > during the merge window as it's a trivial patch removing
> > duplicate defines.
>
> I'm failing to understand what do you mean by that...
> According to Linus ("probably Sunday - I'll be on airplanes next Monday"),
> the merge window will be closed soon.
>
> Do you mean, you will send an updated pull request?
Sorry I meant during the -rc cycle, I guess we're out of
time for the merge window to make changes.
Regards,
Tony
next prev parent reply other threads:[~2011-05-26 12:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 11:39 [GIT PULL] omap updates for 2.6.40 Tony Lindgren
2011-05-26 11:39 ` Tony Lindgren
2011-05-26 12:14 ` Igor Grinberg
2011-05-26 12:14 ` Igor Grinberg
2011-05-26 12:24 ` Tony Lindgren
2011-05-26 12:24 ` Tony Lindgren
2011-05-26 12:52 ` Igor Grinberg
2011-05-26 12:52 ` Igor Grinberg
2011-05-26 12:55 ` Tony Lindgren [this message]
2011-05-26 12:55 ` Tony Lindgren
2011-05-26 16:06 ` Koen Kooi
2011-05-26 16:06 ` Koen Kooi
2011-05-27 6:33 ` Tony Lindgren
2011-05-27 6:33 ` Tony Lindgren
2011-05-27 11:04 ` Tony Lindgren
2011-05-27 11:04 ` Tony Lindgren
2011-05-27 12:22 ` Koen Kooi
2011-05-27 12:22 ` Koen Kooi
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=20110526125529.GC11352@atomide.com \
--to=tony@atomide.com \
--cc=grinberg@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.