From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: reduce conflicts in Kcinfig.debug
Date: Fri, 30 Jan 2015 07:02:51 +0200 [thread overview]
Message-ID: <20150130050251.GN19448@tarshish> (raw)
In-Reply-To: <20150130130117.4d9fbd70@canb.auug.org.au>
Hi Stephen,
On Fri, Jan 30, 2015 at 01:01:17PM +1100, Stephen Rothwell wrote:
> I have seen several conflicts in this file (and other Kconfig files)
> over time, so I suggest a solution like below.
>
> Create new config symbols that can be selected by other configs
> and use them as single dependencies rather than having long lists of
> other config symbols as dependencies.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
For subject: s/Kcinfig/Kconfig/
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2015-01-30 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 2:01 [PATCH] arm: reduce conflicts in Kcinfig.debug Stephen Rothwell
2015-01-30 5:02 ` Baruch Siach [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=20150130050251.GN19448@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).