From: Jonathan Corbet <corbet@lwn.net>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] Documentation: Add MCB documentation
Date: Tue, 7 Jul 2015 08:11:56 -0600 [thread overview]
Message-ID: <20150707081156.6fa4d6a6@lwn.net> (raw)
In-Reply-To: <1436258228-5170-1-git-send-email-jthumshirn@suse.de>
On Tue, 7 Jul 2015 10:37:08 +0200
Johannes Thumshirn <jthumshirn@suse.de> wrote:
> The 1st version of this patch was send on Feb 16
> (https://lkml.org/lkml/2015/2/16/31) and it seems like it missed v4.1 and I
> couldn't find it in the docs-next tree as well, that's the reason for the
> re-send.
Very weird. I replied at the time that I had applied it, but it's sure
not there now. Unless, chameleon-like, it's hiding?
Now that I'm paying attention again, could I ask for a name change for the
file? MCB.txt doesn't really tell anybody anything. How about
chameleon-bus.txt or something like that?
Thanks (and sorry),
jon
next prev parent reply other threads:[~2015-07-07 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 8:37 Johannes Thumshirn
2015-07-07 14:11 ` Jonathan Corbet [this message]
2015-07-08 13:25 ` Johannes Thumshirn
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=20150707081156.6fa4d6a6@lwn.net \
--to=corbet@lwn.net \
--cc=jthumshirn@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®