linux-kernel - Re: linux-next: manual merge of the mmc tree with the block tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 29 Nov 2016 10:22:53 +0100
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     Christoph Hellwig <hch@....de>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>, Jens Axboe <axboe@...com>,
        "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Linus Walleij <linus.walleij@...aro.org>
Subject: Re: linux-next: manual merge of the mmc tree with the block tree

On 29 November 2016 at 10:16, Christoph Hellwig <hch@....de> wrote:
> On Tue, Nov 29, 2016 at 10:13:59AM +0100, Ulf Hansson wrote:
>> Jens, Christoph, I believe I said this before; could you please make
>> sure patches for mmc also becomes cc:ed to me?
>> Don't get me wrong, I have no problem you carrying changes for mmc,
>> especially clean-ups like this one, but it just be nice to be aware of
>> what goes on.
>
> I'm not going to Cc every driver maintainer on trivial tree-wide
> cleanups.  As the maintainer of a block driver you should be subscribed
> to the linux-block mailing list where every block patch is discussed.

Okay!

Kind regards
Uffe