From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Langsdorf <mark.langsdorf@calxeda.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: linux-next: Tree for Sept 14 (sata_highhbank)
Date: Fri, 14 Sep 2012 23:17:48 +0100 [thread overview]
Message-ID: <CAFtxgO5yfDd5bGVZ0a_zTQBZpEKFfJG5UMw03jKSxwbgYnNNZA@mail.gmail.com> (raw)
In-Reply-To: <5053A993.8090408@calxeda.com>
On Fri, Sep 14, 2012 at 11:02 PM, Mark Langsdorf
<mark.langsdorf@calxeda.com> wrote:
> Fix patch follows. Do I need to submit it as a separate patch or is this
> sufficient?
You appear to have submitted it as a separate patch just now ;p
Will queue and push to libata-dev.git#upstream (and thus linux-next)
Jeff
prev parent reply other threads:[~2012-09-14 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 7:38 linux-next: Tree for Sept 14 Stephen Rothwell
2012-09-14 11:56 ` Sedat Dilek
2012-09-14 17:04 ` linux-next: Tree for Sept 14 (sata_highhbank) Randy Dunlap
2012-09-14 22:02 ` Mark Langsdorf
2012-09-14 22:17 ` Jeff Garzik [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=CAFtxgO5yfDd5bGVZ0a_zTQBZpEKFfJG5UMw03jKSxwbgYnNNZA@mail.gmail.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mark.langsdorf@calxeda.com \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).