From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Abraham <thomas.ab@samsung.com>,
ben-linux@fluff.org, linux-arm-kernel@lists.infradead.org,
Thomas Chou <thomas@wytron.com.tw>,
Nios2 development list <nios2-dev@sopc.et.ntust.edu.tw>,
Ian Abbott <abbotti@mev.co.uk>
Subject: Re: [git patches] new hardware support for atang tree
Date: Wed, 03 Feb 2010 14:58:07 -0500 [thread overview]
Message-ID: <4B69D54F.4040705@garzik.org> (raw)
In-Reply-To: <201002031940.20129.bzolnier@gmail.com>
On 02/03/2010 01:40 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Since I haven't seen any progress on mainstreaming of s3c-ide and
> pata_altera_cf patches in the recent months I decided to merge them
pata_altera_cf still needs to be updated to v3, taking into account
Alan's feedback. A ping in Nov 2009 resulted in no response.
Jeff
WARNING: multiple messages have this Message-ID (diff)
From: jeff@garzik.org (Jeff Garzik)
To: linux-arm-kernel@lists.infradead.org
Subject: [git patches] new hardware support for atang tree
Date: Wed, 03 Feb 2010 14:58:07 -0500 [thread overview]
Message-ID: <4B69D54F.4040705@garzik.org> (raw)
In-Reply-To: <201002031940.20129.bzolnier@gmail.com>
On 02/03/2010 01:40 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Since I haven't seen any progress on mainstreaming of s3c-ide and
> pata_altera_cf patches in the recent months I decided to merge them
pata_altera_cf still needs to be updated to v3, taking into account
Alan's feedback. A ping in Nov 2009 resulted in no response.
Jeff
next prev parent reply other threads:[~2010-02-03 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 18:40 [git patches] new hardware support for atang tree Bartlomiej Zolnierkiewicz
2010-02-03 18:40 ` Bartlomiej Zolnierkiewicz
2010-02-03 19:58 ` Jeff Garzik [this message]
2010-02-03 19:58 ` Jeff Garzik
2010-02-04 8:16 ` Ben Dooks
2010-02-04 8:16 ` Ben Dooks
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=4B69D54F.4040705@garzik.org \
--to=jeff@garzik.org \
--cc=abbotti@mev.co.uk \
--cc=ben-linux@fluff.org \
--cc=bzolnier@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@sopc.et.ntust.edu.tw \
--cc=thomas.ab@samsung.com \
--cc=thomas@wytron.com.tw \
/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.