mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hirokazu Takata <takata@linux-m32r.org>
To: Tim Abbott <tabbott@ksplice.com>
Cc: torvalds@linux-foundation.org, linux-m32r@ml.linux-m32r.org,
	linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
	Hirokazu Takata <takata@linux-m32r.org>
Subject: Re: [GIT PULL] m32r: Cleanup linker script
Date: Fri, 25 Sep 2009 09:23:03 +0900	[thread overview]
Message-ID: <swfhburoot4.wl%takata@linux-m32r.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0909241023340.10348@dr-wily.mit.edu>

At Thu, 24 Sep 2009 10:27:06 -0400 (EDT),
Tim Abbott wrote:
> 
> On Wed, 23 Sep 2009, Tim Abbott wrote:
> 
> > On Wed, 23 Sep 2009, Hirokazu Takata wrote:
> > 
> > > Hi, Linus,
> > > 
> > > Sorry, there was a cross in the post.
> > > 
> > > I was not conscious of Sam's acknowledgement mail.  And a newer patchset
> > > has been sent by Tim Abbott on Sep. 22, 2009 - 10:23:21 EST.
> > > 
> > > > [PATCH 00/13] Linker script cleanup patches for various architectures
> > > 
> > > The newer patchset includes updates for not only m32r but also
> > > parisc, xtenza, h8300, mn10300 and um.
> ...
> > The 6 m32r patches I sent to Linus are exactly the same as what's in your 
> > pull request, so it doesn't matter which one gets merged.
> 
> Since I'm resending that patch series to Linus for other reasons today, 
> I'm going to drop the m32r patches from it (so Linus should merge these 
> m32r linker script cleanups from the pull request).
> 
> Sorry again for the confusion.
> 
> 	Best regards,
> 	-Tim Abbott
> 

Thank you very much for your additional effort.

I will send a updated pull request for m32r to Linus again.

Best regards,

-- Takata

      reply	other threads:[~2009-09-25  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 17:55 Hirokazu Takata
2009-09-23  3:06 ` Hirokazu Takata
2009-09-23 13:46   ` Tim Abbott
2009-09-24 14:27     ` Tim Abbott
2009-09-25  0:23       ` Hirokazu Takata [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=swfhburoot4.wl%takata@linux-m32r.org \
    --to=takata@linux-m32r.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m32r@ml.linux-m32r.org \
    --cc=sam@ravnborg.org \
    --cc=tabbott@ksplice.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®