Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Tim Gardner <tim.gardner@canonical.com>,
	linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	dann frazier <dann.frazier@canonical.com>
Subject: Re: linux-next: ahci_platform broken build
Date: Sun, 16 Mar 2014 10:54:57 -0400	[thread overview]
Message-ID: <20140316145457.GA26026@htj.dyndns.org> (raw)
In-Reply-To: <5325B1A3.9070102@redhat.com>

On Sun, Mar 16, 2014 at 03:13:55PM +0100, Hans de Goede wrote:
> Tejun it is probably easiest if you fix this up directly in your tree, let me know if you
> want a fixed up resend of the 2 patches in question instead.

It already happened and got resolved in the span of few patches.  Shit
happens.  Let's just try to test each step better next time.

Thanks.

-- 
tejun

      reply	other threads:[~2014-03-16 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 14:05 linux-next: ahci_platform broken build Tim Gardner
2014-03-16 14:13 ` Hans de Goede
2014-03-16 14:54   ` Tejun Heo [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=20140316145457.GA26026@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=dann.frazier@canonical.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.gardner@canonical.com \
    /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