From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org
Cc: devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
John Williams
<john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Subject: Re: [GIT PULL] arch/microblaze fixes for 2.6.34-rc2
Date: Sat, 20 Mar 2010 11:35:36 -0600 [thread overview]
Message-ID: <fa686aa41003201035r3d95b780naf37a4725293d648@mail.gmail.com> (raw)
In-Reply-To: <4B98F32D.8020906-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
On Thu, Mar 11, 2010 at 6:42 AM, Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org> wrote:
> Hi Linus,
>
> Please pull Microblaze changes to your tree. There is support for PCI and
> new DMA interface.
>
> Thanks,
> Michal
Hi Michal.
I'm really unimpressed that you've merged the cloned PCI support code
when we talked about merging the common powerpc & microblaze bits
/before/ pushing it up to mainline. At the very least I would have
expected a reply back from you telling me that you disagree and that
you wanted to merge anyway. I didn't even get a reply back form you
when I asked about why the PCI bits were in your linux-next branch.
Now it needs to be merged in-place which is a lot more work.
g.
next parent reply other threads:[~2010-03-20 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B98F32D.8020906@monstr.eu>
[not found] ` <4B98F32D.8020906-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2010-03-20 17:35 ` Grant Likely [this message]
[not found] ` <fa686aa41003201035r3d95b780naf37a4725293d648-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-21 22:32 ` [GIT PULL] arch/microblaze fixes for 2.6.34-rc2 John Williams
[not found] ` <1d3f23371003211532p57fe0785s5960ddea8218d4d4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-27 1:37 ` Grant Likely
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=fa686aa41003201035r3d95b780naf37a4725293d648@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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