From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Mike Snitzer <snitzer@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Damien Le Moal <damien.lemoal@wdc.com>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
dm-devel@redhat.com, Christoph Hellwig <hch@lst.de>,
Matias Bjorling <matias.bjorling@wdc.com>
Subject: Re: [PATCH v4 00/11] Zoned block device support improvements
Date: Wed, 24 Oct 2018 09:04:53 -0700 [thread overview]
Message-ID: <1540397093.66186.13.camel@acm.org> (raw)
In-Reply-To: <yq1zhv3e4oe.fsf@oracle.com>
On Wed, 2018-10-24 at 11:37 -0400, Martin K. Petersen wrote:
> Mike,
>
> > > You keep mentioning this, but I don't recall ever seeing anything to
> > > that effect. The rest of the kernel appears to be either arbitrary
> > > ordering or favoring author SoB as the first tag.
> >
> > I've always felt the proper order is how Jens likes it too (all dm
> > commits from me follow that order).
>
> That's fine, I don't have any particular preference. And I don't have
> any issue with you guys sticking to a certain ordering in your
> respective subsystems. I occasionally shuffle tags when I commit things
> in SCSI too.
>
> I just think it should be properly documented if there is a preferred
> way to order things...
When I tried to look up documentation for this I couldn't find anything under
the Documentation directory. Maybe it's there but I didn't look carefully
enough. All I could find on the web is e-mails from Linus in which he explains
that the order of Signed-off-by's should match the chain of authorship.
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Mike Snitzer <snitzer@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Damien Le Moal <damien.lemoal@wdc.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
dm-devel@redhat.com, Christoph Hellwig <hch@lst.de>,
Matias Bjorling <matias.bjorling@wdc.com>
Subject: Re: [PATCH v4 00/11] Zoned block device support improvements
Date: Wed, 24 Oct 2018 09:04:53 -0700 [thread overview]
Message-ID: <1540397093.66186.13.camel@acm.org> (raw)
In-Reply-To: <yq1zhv3e4oe.fsf@oracle.com>
On Wed, 2018-10-24 at 11:37 -0400, Martin K. Petersen wrote:
> Mike,
>
> > > You keep mentioning this, but I don't recall ever seeing anything to
> > > that effect. The rest of the kernel appears to be either arbitrary
> > > ordering or favoring author SoB as the first tag.
> >
> > I've always felt the proper order is how Jens likes it too (all dm
> > commits from me follow that order).
>
> That's fine, I don't have any particular preference. And I don't have
> any issue with you guys sticking to a certain ordering in your
> respective subsystems. I occasionally shuffle tags when I commit things
> in SCSI too.
>
> I just think it should be properly documented if there is a preferred
> way to order things...
When I tried to look up documentation for this I couldn't find anything under
the Documentation directory. Maybe it's there but I didn't look carefully
enough. All I could find on the web is e-mails from Linus in which he explains
that the order of Signed-off-by's should match the chain of authorship.
Bart.
next prev parent reply other threads:[~2018-10-24 16:04 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 10:08 [PATCH v4 00/11] Zoned block device support improvements Damien Le Moal
2018-10-12 10:08 ` [PATCH v4 01/11] scsi: sd_zbc: Rearrange code Damien Le Moal
2018-10-16 4:48 ` Martin K. Petersen
2018-10-16 4:48 ` Martin K. Petersen
2018-10-12 10:08 ` [PATCH v4 02/11] scsi: sd_zbc: Reduce boot device scan and revalidate time Damien Le Moal
2018-10-16 4:50 ` Martin K. Petersen
2018-10-16 4:50 ` Martin K. Petersen
2018-10-12 10:08 ` [PATCH v4 03/11] scsi: sd_zbc: Fix sd_zbc_check_zones() error checks Damien Le Moal
2018-10-12 10:23 ` Hannes Reinecke
2018-10-12 10:23 ` Hannes Reinecke
2018-10-12 11:41 ` Damien Le Moal
2018-10-12 11:41 ` Damien Le Moal
2018-10-16 4:51 ` Martin K. Petersen
2018-10-16 4:51 ` Martin K. Petersen
2018-10-17 7:21 ` Christoph Hellwig
2018-10-17 7:21 ` Christoph Hellwig
2018-10-12 10:08 ` [PATCH v4 04/11] block: Introduce blkdev_nr_zones() helper Damien Le Moal
2018-10-12 10:08 ` [PATCH v4 05/11] block: Limit allocation of zone descriptors for report zones Damien Le Moal
2018-10-12 10:08 ` [PATCH v4 06/11] block: Introduce BLKGETZONESZ ioctl Damien Le Moal
2018-10-12 10:08 ` [PATCH v4 07/11] block: Introduce BLKGETNRZONES ioctl Damien Le Moal
2018-10-12 10:08 ` [PATCH v4 08/11] block: Improve zone reset execution Damien Le Moal
2018-10-12 10:08 ` [PATCH v4 09/11] block: Expose queue nr_zones in sysfs Damien Le Moal
2018-10-12 10:08 ` [PATCH v4 10/11] block: add a report_zones method Damien Le Moal
2018-10-16 4:55 ` Martin K. Petersen
2018-10-16 4:55 ` Martin K. Petersen
2018-10-16 15:17 ` Mike Snitzer
2018-10-16 15:17 ` Mike Snitzer
2018-10-12 10:08 ` [PATCH v4 11/11] block: Introduce blk_revalidate_disk_zones() Damien Le Moal
2018-10-16 5:00 ` Martin K. Petersen
2018-10-16 5:00 ` Martin K. Petersen
2018-10-16 15:17 ` Mike Snitzer
2018-10-16 15:17 ` Mike Snitzer
2018-10-13 22:43 ` [PATCH v4 00/11] Zoned block device support improvements Jens Axboe
2018-10-15 0:45 ` Damien Le Moal
2018-10-15 0:45 ` Damien Le Moal
2018-10-16 2:34 ` Jens Axboe
2018-10-16 3:43 ` Damien Le Moal
2018-10-16 3:43 ` Damien Le Moal
2018-10-18 7:57 ` Damien Le Moal
2018-10-18 7:57 ` Damien Le Moal
2018-10-23 15:59 ` Jens Axboe
2018-10-24 2:26 ` Martin K. Petersen
2018-10-24 2:26 ` Martin K. Petersen
2018-10-24 15:03 ` Mike Snitzer
2018-10-24 15:03 ` Mike Snitzer
2018-10-24 15:37 ` Martin K. Petersen
2018-10-24 15:37 ` Martin K. Petersen
2018-10-24 16:04 ` Bart Van Assche [this message]
2018-10-24 16:04 ` Bart Van Assche
2018-10-25 14:30 ` Jens Axboe
2018-10-25 14:30 ` Jens Axboe
2018-10-24 8:04 ` Damien Le Moal
2018-10-24 8:04 ` 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=1540397093.66186.13.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matias.bjorling@wdc.com \
--cc=snitzer@redhat.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 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.