From: Jesper Nilsson <jesper.nilsson@axis.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Mikael Starvik <starvik@axis.com>,
linux-cris-kernel <linux-cris-kernel@axis.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 21/21] cris: drop unused Kconfig symbols
Date: Mon, 31 Oct 2011 11:59:59 +0100 [thread overview]
Message-ID: <20111031105959.GA26898@axis.com> (raw)
In-Reply-To: <14215.1318619461@turing-police.cc.vt.edu>
Sorry for the late answer, I've been in-flight my self.
On Fri, Oct 14, 2011 at 09:11:01PM +0200, Valdis.Kletnieks@vt.edu wrote:
> Shouldn't the patches that upstream those drivers be the ones to add the
> Kconfig glue? Or is this a case of "in-flight driver" where the submission is
> literally in the middle of getting merged so some parts have landed and some
> haven't yet, and all will be good in the next merge cycle?
You are of course correct that the driver patches should be
ones that add the Kconfigs.
The drivers have been in-flight for quite a while, but without any
push from us, I'll try to give it some love, and at least get it into
a separate tree.
> (Personally, I'm tending towards unless it's going to be in linux-next within
> the next month or so, pull the Kconfig variables out and the driver can re-add
> them when it actually lands)
Ok, let's do it the right way and remove them now, and I can re-add
them in the same tree.
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
next prev parent reply other threads:[~2011-10-31 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 12:31 [PATCH 21/21] cris: drop unused Kconfig symbols Paul Bolle
2011-10-14 13:33 ` Jesper Nilsson
2011-10-14 14:05 ` Paul Bolle
2011-10-14 19:11 ` Valdis.Kletnieks
2011-10-31 10:59 ` Jesper Nilsson [this message]
2013-03-23 13:14 ` Paul Bolle
2013-04-15 15:11 ` Jesper Nilsson
2013-04-16 8:34 ` [PATCH v2] " Paul Bolle
2013-04-16 13:46 ` Jesper Nilsson
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=20111031105959.GA26898@axis.com \
--to=jesper.nilsson@axis.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=starvik@axis.com \
/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