public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Michal Marek <mmarek@suse.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mikael Starvik <starvik@axis.com>,
	"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH 00/17] drop unused Kconfig symbols
Date: Tue, 1 Nov 2011 09:59:30 +0100	[thread overview]
Message-ID: <20111101085930.GF26898@axis.com> (raw)
In-Reply-To: <1320101716.14409.97.camel@x61.thuisdomein>

On Mon, Oct 31, 2011 at 11:55:16PM +0100, Paul Bolle wrote:
> On Mon, 2011-10-31 at 23:42 +0100, Michal Marek wrote:
> > On Mon, Oct 24, 2011 at 01:37:35PM +0200, Paul Bolle wrote:
> > > 1) I've dropped five patches that were taken by the maintainers
> > > (blackfin, unicore32, tomoyo, m68k, and staging). cris got a NAK (for an
> > > invalid reason, but I guess I'll just try again after the v3.2 merge
> > > window closes).
> 
> Just today Jesper Nilsson basically dropped that NAK. I assume Jesper
> will try to carry the patch in (one of) their tree(s). Is that correct?

The patch that reintroduces the Kconfigs, yes, the one that removes them, no.

> Paul Bolle

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

  reply	other threads:[~2011-11-01  8:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1319456255.2409.30.camel@x61.thuisdomein>
2011-10-31 22:42 ` [PATCH 00/17] drop unused Kconfig symbols Michal Marek
2011-10-31 22:55   ` Paul Bolle
2011-11-01  8:59     ` Jesper Nilsson [this message]
2011-11-01  9:46       ` Paul Bolle
2011-11-01 10:12         ` Jesper Nilsson
2011-11-01 10:35           ` Paul Bolle

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=20111101085930.GF26898@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --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