From: Michal Marek <mmarek@suse.com>
To: Jan Beulich <JBeulich@suse.com>, Michal Sojka <sojkam1@fel.cvut.cz>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
trivial@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, Martin Walch <walch.martin@web.de>
Subject: Re: [PATCH] kconfig: Fix copy&paste error
Date: Tue, 20 Oct 2015 19:15:41 +0200 [thread overview]
Message-ID: <562676BD.4090303@suse.com> (raw)
In-Reply-To: <5625210102000078000AC6EA@prv-mh.provo.novell.com>
Dne 19.10.2015 v 16:57 Jan Beulich napsal(a):
>>>> On 19.10.15 at 16:51, <sojkam1@fel.cvut.cz> wrote:
>> Signed-off-by: Michal Sojka <sojkam1@fel.cvut.cz>
>
> Oops - yes of course. Thanks.
>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
Applied to kbuild.git#kconfig.
Michal
prev parent reply other threads:[~2015-10-20 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 14:51 [PATCH] kconfig: Fix copy&paste error Michal Sojka
2015-10-19 14:57 ` Jan Beulich
2015-10-20 17:15 ` Michal Marek [this message]
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=562676BD.4090303@suse.com \
--to=mmarek@suse.com \
--cc=JBeulich@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sojkam1@fel.cvut.cz \
--cc=trivial@kernel.org \
--cc=walch.martin@web.de \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).