All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Andy Gross <andy.gross@linaro.org>,
	Hans de Goede <hdegoede@redhat.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, jmaggard10@gmail.com
Subject: Re: [RFC PATCH 1/3] libahci: save port map for forced port map
Date: Thu, 31 Mar 2016 17:51:42 +0100	[thread overview]
Message-ID: <56FD559E.1090802@linaro.org> (raw)
In-Reply-To: <20160331164328.GA24661@htj.duckdns.org>



On 31/03/16 17:43, Tejun Heo wrote:
> Hello,
>
> On Thu, Mar 31, 2016 at 04:58:27PM +0100, Srinivas Kandagatla wrote:
>> Yes, that is the intention, I guess, This was done exactly in case where the
>> port number was fabricated too.
>>
>> Without this I could not get the sata working on my board with forced port
>> map option.
>
> I see.  Looks good to me then.  Can you please respin the patches with
> the updates for the review points in the second patch?  I'll apply
> them to libata/for-3.6-fixes.

Thanks, I will do it now.

--srini
>
> Thanks.
>

WARNING: multiple messages have this Message-ID (diff)
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/3] libahci: save port map for forced port map
Date: Thu, 31 Mar 2016 17:51:42 +0100	[thread overview]
Message-ID: <56FD559E.1090802@linaro.org> (raw)
In-Reply-To: <20160331164328.GA24661@htj.duckdns.org>



On 31/03/16 17:43, Tejun Heo wrote:
> Hello,
>
> On Thu, Mar 31, 2016 at 04:58:27PM +0100, Srinivas Kandagatla wrote:
>> Yes, that is the intention, I guess, This was done exactly in case where the
>> port number was fabricated too.
>>
>> Without this I could not get the sata working on my board with forced port
>> map option.
>
> I see.  Looks good to me then.  Can you please respin the patches with
> the updates for the review points in the second patch?  I'll apply
> them to libata/for-3.6-fixes.

Thanks, I will do it now.

--srini
>
> Thanks.
>

  reply	other threads:[~2016-03-31 16:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 13:11 [RFC PATCH 0/3] ahci: add ports-implemented dt bindings Srinivas Kandagatla
2016-03-29 13:11 ` Srinivas Kandagatla
2016-03-29 13:11 ` [RFC PATCH 1/3] libahci: save port map for forced port map Srinivas Kandagatla
2016-03-29 13:11   ` Srinivas Kandagatla
2016-03-30 18:57   ` Tejun Heo
2016-03-30 18:57     ` Tejun Heo
2016-03-31 15:58     ` Srinivas Kandagatla
2016-03-31 15:58       ` Srinivas Kandagatla
2016-03-31 16:43       ` Tejun Heo
2016-03-31 16:43         ` Tejun Heo
2016-03-31 16:51         ` Srinivas Kandagatla [this message]
2016-03-31 16:51           ` Srinivas Kandagatla
2016-03-29 13:11 ` [RFC PATCH 2/3] ata: ahci-platform: Add ports-implemented dt bindings Srinivas Kandagatla
2016-03-29 13:11   ` Srinivas Kandagatla
2016-03-29 14:11   ` Rob Herring
2016-03-29 14:11     ` Rob Herring
2016-03-29 14:43     ` Srinivas Kandagatla
2016-03-29 14:43       ` Srinivas Kandagatla
2016-03-29 14:43       ` Srinivas Kandagatla
2016-03-29 17:07       ` Rob Herring
2016-03-29 17:07         ` Rob Herring
2016-03-29 17:10         ` Srinivas Kandagatla
2016-03-29 17:10           ` Srinivas Kandagatla
2016-03-29 13:11 ` [RFC PATCH 3/3] ARM: dts: apq8064: add ahci ports-implemented mask Srinivas Kandagatla
2016-03-29 13:11   ` Srinivas Kandagatla

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=56FD559E.1090802@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=jmaggard10@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tj@kernel.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 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.