From: Greg KH <gregkh@suse.de>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: linux-next@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] staging: really fix up Kconfig automatic deselction
Date: Mon, 8 Dec 2008 19:54:44 -0800 [thread overview]
Message-ID: <20081209035444.GA22626@suse.de> (raw)
In-Reply-To: <1228785051-12954-1-git-send-email-dbaryshkov@gmail.com>
On Tue, Dec 09, 2008 at 04:10:51AM +0300, Dmitry Eremin-Solenikov wrote:
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
This patch should be used instead of your current one in my tree, right?
Or apply it on top of your current one?
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-09 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 9:43 linux-next: staging tree build failure Stephen Rothwell
2008-12-08 10:34 ` Dmitry Baryshkov
2008-12-08 15:08 ` Greg KH
2008-12-09 1:10 ` [PATCH] staging: really fix up Kconfig automatic deselction Dmitry Eremin-Solenikov
2008-12-09 3:54 ` Greg KH [this message]
2008-12-09 4:32 ` Dmitry Eremin-Solenikov
2008-12-12 18:55 ` Greg KH
2008-12-11 8:37 ` linux-next: staging tree build failure Stephen Rothwell
2008-12-12 18:55 ` Greg KH
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=20081209035444.GA22626@suse.de \
--to=gregkh@suse.de \
--cc=dbaryshkov@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).