From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC PATCH 2/2] block: revert "block: fix bd_size_lock use"
Date: Thu, 4 Feb 2021 09:16:13 +0000 [thread overview]
Message-ID: <BL0PR04MB65145DD0F6889359E6321985E7B39@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: SN4PR0401MB359820BA20257B72EDFBA3499BB39@SN4PR0401MB3598.namprd04.prod.outlook.com
On 2021/02/04 18:14, Johannes Thumshirn wrote:
> On 04/02/2021 10:03, Damien Le Moal wrote:
>> On 2021/02/04 18:01, Johannes Thumshirn wrote:
>>> Given that #1 in this series is accepted,
>>> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>>>
>>
>> Do you mean "if #1 in this series is accepted" ?
>> I have not received patch #1... I wonder if it hit the list ? Did you get it ?
>>
>
> Me neither, seems like vger is acting funny again
Or Exchange is again acting up. It does not show up in lore... Resending.
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2021-02-04 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 8:43 [RFC PATCH 0/2] block: Remove skd driver Damien Le Moal
2021-02-04 8:43 ` [RFC PATCH 2/2] block: revert "block: fix bd_size_lock use" Damien Le Moal
2021-02-04 9:01 ` Johannes Thumshirn
2021-02-04 9:03 ` Damien Le Moal
2021-02-04 9:14 ` Johannes Thumshirn
2021-02-04 9:16 ` Damien Le Moal [this message]
2021-02-04 9:20 ` Damien Le Moal
2021-02-04 9:25 ` Johannes Thumshirn
2021-02-04 9:26 ` Damien Le Moal
2021-02-04 14:46 ` [RFC PATCH 0/2] block: Remove skd driver Jens Axboe
2021-02-04 14:52 ` Damien Le Moal
2021-02-04 14:54 ` Jens Axboe
2021-02-04 14:57 ` 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=BL0PR04MB65145DD0F6889359E6321985E7B39@BL0PR04MB6514.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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 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.