From: Jens Axboe <axboe@kernel.dk>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: stable@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
linux-nvdimm@lists.01.org
Subject: Re: [PATCH] loop: Fix lost writes caused by missing flag
Date: Fri, 9 Mar 2018 10:19:16 -0700 [thread overview]
Message-ID: <fa45f4eb-7003-bd6a-471c-fbfe16abcd72@kernel.dk> (raw)
In-Reply-To: <20180309163554.GA485@linux.intel.com>
On 3/9/18 9:35 AM, Ross Zwisler wrote:
> On Fri, Mar 09, 2018 at 08:38:57AM -0700, Jens Axboe wrote:
>> On 3/9/18 8:38 AM, Jens Axboe wrote:
>>> On 3/8/18 5:20 PM, Ross Zwisler wrote:
>>>> This has gotten Reviewed-by tags from Christoph and Ming Lei.
>>>>
>>>> Al, are you the right person to merge this? Or is the correct person Jens,
>>>> whom I accidentally didn't include when I sent this out?
>>>>
>>>> Just wanted to make sure this got merged, and to see whether it was targeting
>>>> v4.16 or v4.17.
>>>
>>> I'm the right guy, but I don't see patches if I'm not cc'ed on them...
>>> I have queued this up for 4.16, thanks.
>>
>> I do see patches sent to linux-block aswell, but you didn't CC that one
>> either.
>
> I figure out who to CC on my patches by using scripts/get_maintainer.pl, and
> it didn't know about you or linux-block because drivers/block wasn't covered
> in MAINTAINERS. I'll send a patch to fix this.
I'm the first person for a check on drivers/block/ or
drivers/block/loop.c, though...
> As it was I just CC'd the folks involved in the original patch, and that one
> went up through Al.
>
> Thanks for picking this up.
No problem, glad it worked out.
--
Jens Axboe
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
stable@vger.kernel.org
Subject: Re: [PATCH] loop: Fix lost writes caused by missing flag
Date: Fri, 9 Mar 2018 10:19:16 -0700 [thread overview]
Message-ID: <fa45f4eb-7003-bd6a-471c-fbfe16abcd72@kernel.dk> (raw)
In-Reply-To: <20180309163554.GA485@linux.intel.com>
On 3/9/18 9:35 AM, Ross Zwisler wrote:
> On Fri, Mar 09, 2018 at 08:38:57AM -0700, Jens Axboe wrote:
>> On 3/9/18 8:38 AM, Jens Axboe wrote:
>>> On 3/8/18 5:20 PM, Ross Zwisler wrote:
>>>> This has gotten Reviewed-by tags from Christoph and Ming Lei.
>>>>
>>>> Al, are you the right person to merge this? Or is the correct person Jens,
>>>> whom I accidentally didn't include when I sent this out?
>>>>
>>>> Just wanted to make sure this got merged, and to see whether it was targeting
>>>> v4.16 or v4.17.
>>>
>>> I'm the right guy, but I don't see patches if I'm not cc'ed on them...
>>> I have queued this up for 4.16, thanks.
>>
>> I do see patches sent to linux-block aswell, but you didn't CC that one
>> either.
>
> I figure out who to CC on my patches by using scripts/get_maintainer.pl, and
> it didn't know about you or linux-block because drivers/block wasn't covered
> in MAINTAINERS. I'll send a patch to fix this.
I'm the first person for a check on drivers/block/ or
drivers/block/loop.c, though...
> As it was I just CC'd the folks involved in the original patch, and that one
> went up through Al.
>
> Thanks for picking this up.
No problem, glad it worked out.
--
Jens Axboe
next prev parent reply other threads:[~2018-03-09 17:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 23:05 [PATCH] loop: Fix lost writes caused by missing flag Ross Zwisler
2018-02-12 23:05 ` Ross Zwisler
2018-02-13 14:54 ` Christoph Hellwig
2018-02-13 14:54 ` Christoph Hellwig
2018-02-13 19:22 ` Ross Zwisler
2018-02-13 19:22 ` Ross Zwisler
2018-02-13 20:52 ` Dan Williams
2018-02-13 20:52 ` Dan Williams
2018-02-22 3:21 ` Ming Lei
2018-02-22 3:21 ` Ming Lei
2018-03-09 0:20 ` Ross Zwisler
2018-03-09 0:20 ` Ross Zwisler
2018-03-09 15:38 ` Jens Axboe
2018-03-09 15:38 ` Jens Axboe
2018-03-09 15:38 ` Jens Axboe
2018-03-09 15:38 ` Jens Axboe
2018-03-09 16:35 ` Ross Zwisler
2018-03-09 16:35 ` Ross Zwisler
2018-03-09 17:19 ` Jens Axboe [this message]
2018-03-09 17:19 ` Jens Axboe
2018-03-09 16:38 ` [PATCH] MAINTAINERS: add coverage for drivers/block Ross Zwisler
2018-03-09 16:38 ` Ross Zwisler
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=fa45f4eb-7003-bd6a-471c-fbfe16abcd72@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.