public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michael.christie@oracle.com>
To: Dmitry Bogdanov <d.bogdanov@yadro.com>,
	Martin Petersen <martin.petersen@oracle.com>,
	target-devel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-scsi@vger.kernel.org, linux@yadro.com,
	Roman Bolshakov <r.bolshakov@yadro.com>
Subject: Re: [PATCH v3 5/5] scsi: target: core: Add RTPI attribute for target port
Date: Tue, 20 Dec 2022 18:15:53 -0600	[thread overview]
Message-ID: <8e97531d-da78-6599-26c2-631d7a73c48e@oracle.com> (raw)
In-Reply-To: <20221202121139.28180-6-d.bogdanov@yadro.com>

On 12/2/22 6:11 AM, Dmitry Bogdanov wrote:
> RELATIVE TARGET PORT IDENTIFIER can be read and configured via configfs:
> $ echo 0x10 > $TARGET/tpgt_N/attrib/rtpi
> 

Hey Dimitry, I think your idea to place this on the tpgt_n is nicer
because you can more easily set it and there is already code for
that type of thing.


      parent reply	other threads:[~2022-12-21  0:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 12:11 [PATCH v3 0/5] scsi: target: make RTPI an TPG identifier Dmitry Bogdanov
2022-12-02 12:11 ` [PATCH v3 1/5] scsi: target: core: Add RTPI field to target port Dmitry Bogdanov
2022-12-02 15:14   ` kernel test robot
2022-12-02 12:11 ` [PATCH v3 2/5] scsi: target: core: Use RTPI from " Dmitry Bogdanov
2022-12-02 12:11 ` [PATCH v3 3/5] scsi: target: core: Drop device-based RTPI Dmitry Bogdanov
2022-12-02 12:11 ` [PATCH v3 4/5] scsi: target: core: Add common port attributes Dmitry Bogdanov
2022-12-02 12:11 ` [PATCH v3 5/5] scsi: target: core: Add RTPI attribute for target port Dmitry Bogdanov
2022-12-02 17:05   ` kernel test robot
2022-12-02 19:17   ` kernel test robot
2022-12-02 21:18   ` kernel test robot
2022-12-21  0:15   ` Mike Christie [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=8e97531d-da78-6599-26c2-631d7a73c48e@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=d.bogdanov@yadro.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@yadro.com \
    --cc=martin.petersen@oracle.com \
    --cc=r.bolshakov@yadro.com \
    --cc=target-devel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox