From: Dominik Brodowski <linux@dominikbrodowski•net>
To: Russell King <rmk+lkml@arm•linux.org.uk>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Dmitry Artamonow <mad_soft@inbox•ru>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: manual merge of the pcmcia tree with the arm tree
Date: Sat, 5 Dec 2009 12:07:21 +0100 [thread overview]
Message-ID: <20091205110721.GB23213@isilmar.linta.de> (raw)
In-Reply-To: <20091205103038.GA11140@flint.arm.linux.org.uk>
On Sat, Dec 05, 2009 at 10:30:38AM +0000, Russell King wrote:
> On Thu, Dec 03, 2009 at 09:25:25AM +1100, Stephen Rothwell wrote:
> > Hi Dmitry,
> >
> > On Wed, 2 Dec 2009 14:56:49 +0300 Dmitry Artamonow <mad_soft@inbox•ru> wrote:
> > >
> > > Fix looks good to me, and testing next-20091201 on real device (h3600)
> > > shows no problems with pcmcia.
> >
> > Thanks for the confirmation.
>
> Since Dominik has been ignoring this issue, and has already asked Linus to
> pull his tree with my (unfortunately just discovered buggy) changes in, I'm
> going to drop the H3600 PCMCIA changes until something can be sorted out.
Well, I hope that Linus merges the first bunch of PCMCIA changes soon, so
that we have a clean base to work from and to sort the dependecies in
ARM-related patches out.
Best,
Dominik
next prev parent reply other threads:[~2009-12-05 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 3:03 linux-next: manual merge of the pcmcia tree with the arm tree Stephen Rothwell
2009-12-02 11:56 ` Dmitry Artamonow
2009-12-02 22:25 ` Stephen Rothwell
2009-12-05 10:30 ` Russell King
2009-12-05 11:07 ` Dominik Brodowski [this message]
2009-12-06 16:51 ` Dmitry Artamonow
2009-12-03 17:04 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2012-03-05 3:22 Stephen Rothwell
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=20091205110721.GB23213@isilmar.linta.de \
--to=linux@dominikbrodowski$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mad_soft@inbox$(echo .)ru \
--cc=rmk+lkml@arm$(echo .)linux.org.uk \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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