The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: yangxingui <yangxingui@huawei.com>
To: Jason Yan <yanaijie@huawei.com>,
	John Garry <john.g.garry@oracle.com>,
	Damien Le Moal <dlemoal@kernel.org>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>, <damien.lemoal@opensource.wdc.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linuxarm@huawei.com>, <prime.zeng@hisilicon.com>,
	<kangfenglong@huawei.com>
Subject: Re: [PATCH v2] ata: libata-scsi: Fix get identity data failed
Date: Sat, 6 May 2023 17:49:00 +0800	[thread overview]
Message-ID: <0b4dee69-347f-4a53-d41d-5a0de96d9b2f@huawei.com> (raw)
In-Reply-To: <4364409d-e63c-f87f-0484-f170e92d44c5@huawei.com>



On 2023/5/6 10:11, Jason Yan wrote:
> On 2023/5/5 17:14, yangxingui wrote:
>>
>>
>> On 2023/5/5 16:25, John Garry wrote:
>>> On 05/05/2023 09:17, Damien Le Moal wrote:
>>>>> --- a/drivers/ata/libata-scsi.c
>>>>> +++ b/drivers/ata/libata-scsi.c
>>>>> @@ -26,6 +26,7 @@
>>>>>   #include <scsi/scsi_device.h>
>>>>>   #include <scsi/scsi_tcq.h>
>>>>>   #include <scsi/scsi_transport.h>
>>>>> +#include <scsi/libsas.h>
>>>
>>> hmmm... is it really acceptable that libata is referencing libsas? I 
>>> didn't think that it would be. libsas uses libata, not the other way 
>>> around.
>> Yeah, I didn't expect that either. Is there any other way? If so, is 
>> patch v1 OK?
> 
> Hi Xingui,
> 
> Libsas should follow the standard way of libata to manage the ata 
> structures. Not the opposite way. So what you should do is to find a way 
> for libsas to behave as a normal ata driver. It's not good to make 
> libata aware of libsas or referencing libsas.
> 
> If you have detailed questions you can ask me internally(which will be 
> faster) or publicly through the maillist(which may have some delay).
> 
ok

Thanks,
Xingui
.
> Thanks,
> Jason
> .

  reply	other threads:[~2023-05-06  9:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  2:57 [PATCH v2] ata: libata-scsi: Fix get identity data failed Xingui Yang
2023-05-05  8:17 ` Damien Le Moal
2023-05-05  8:25   ` John Garry
2023-05-05  9:14     ` yangxingui
2023-05-05  9:51       ` John Garry
2023-05-06  9:57         ` yangxingui
2023-05-07 15:02         ` Damien Le Moal
2023-05-06  2:11       ` Jason Yan
2023-05-06  9:49         ` yangxingui [this message]
2023-05-07 14:59       ` Damien Le Moal
2023-05-05  9:06   ` yangxingui
2023-05-07 14:51     ` Damien Le Moal
2023-05-08  1:11       ` yangxingui
2023-05-22  1:35         ` Damien Le Moal
2023-05-22  7:02           ` Damien Le Moal
2023-05-22  8:00             ` Jason Yan
2023-05-22  9:44               ` Damien Le Moal
2023-05-22 11:28               ` John Garry
2023-05-22 11:47                 ` Damien Le Moal

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=0b4dee69-347f-4a53-d41d-5a0de96d9b2f@huawei.com \
    --to=yangxingui@huawei.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dlemoal@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=john.g.garry@oracle.com \
    --cc=kangfenglong@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=martin.petersen@oracle.com \
    --cc=prime.zeng@hisilicon.com \
    --cc=yanaijie@huawei.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