From: Christoph Hellwig <hch@lst.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@fb.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: linux-next: manual merge of the mmc tree with the block tree
Date: Tue, 29 Nov 2016 10:16:32 +0100 [thread overview]
Message-ID: <20161129091632.GA6527@lst.de> (raw)
In-Reply-To: <CAPDyKFrRFOhaQPedRO_2BSinA=cWTza2tHAnP7oPFGKzW5E2Wg@mail.gmail.com>
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.
next prev parent reply other threads:[~2016-11-29 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 2:12 linux-next: manual merge of the mmc tree with the block tree Stephen Rothwell
2016-11-29 9:13 ` Ulf Hansson
2016-11-29 9:16 ` Christoph Hellwig [this message]
2016-11-29 9:22 ` Ulf Hansson
-- strict thread matches above, loose matches on Subject: below --
2017-06-13 4:19 Stephen Rothwell
2022-05-11 2:42 Stephen Rothwell
2024-02-20 1:01 Stephen Rothwell
2024-02-20 8:04 ` Christoph Hellwig
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=20161129091632.GA6527@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ulf.hansson@linaro.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