mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org,
	"Antoine Tenart" <antoine.tenart@free-electrons.com>,
	"Joachim Eastwood" <manabian@gmail.com>,
	"Masahiro Yamada" <yamada.masahiro@socionext.com>,
	"Maxime Ripard" <maxime.ripard@free-electrons.com>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Moritz Fischer" <moritz.fischer@ettus.com>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	"Steffen Trumtrar" <s.trumtrar@pengutronix.de>
Subject: Re: [PATCH 0/5] reset: make non-modular drivers really non modular
Date: Mon, 24 Oct 2016 10:56:45 +0200	[thread overview]
Message-ID: <1477299405.2446.9.camel@pengutronix.de> (raw)
In-Reply-To: <20161022214857.GO3147@windriver.com>

Hi Paul,

Am Samstag, den 22.10.2016, 17:48 -0400 schrieb Paul Gortmaker:
> [[PATCH 0/5] reset: make non-modular drivers really non modular] On 13/06/2016 (Mon 14:03) Paul Gortmaker wrote:
> 
> > For anyone new to the underlying goal of this cleanup, we are trying to
> > not use module support for code that can never be built as a module since:
> 
> Hi Philipp,
> 
> I sent this several months ago, and aside from a couple Ack'd by, there
> was no negative feedback or similar.
> 
> Since then there have been two more drivers added with the same issue.
> 
> 	reset-make-ath79-explicitly-non-modular.patch
> 	reset-pistachio-make-it-explicitly-non-modular.patch
> 
> Should I assume that the original send has fallen through the cracks and
> resend with the two new patches, or do you still have the original five
> in a queue somewhere?

thanks for the reminder. I had them stashed away because I wanted to see
whether the introduction of per-driver Kconfig options would change some
of them to become modular. That wasn't the case, so I have pushed your
patches to the reset/next branch now, with fixed up commit messages.

> I'd like to merge as many of these as I can via their respective
> maintainers vs. trying to send them to Linus directly.
> 
> Thanks,
> Paul.

regards
Philipp

      reply	other threads:[~2016-10-24  8:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 18:03 Paul Gortmaker
2016-06-13 18:03 ` [PATCH 1/5] reset: berlin: make it explicitly non-modular Paul Gortmaker
2016-06-13 18:03 ` [PATCH 2/5] reset: socfpga: " Paul Gortmaker
2016-06-13 18:03 ` [PATCH 3/5] reset: sunxi: " Paul Gortmaker
2016-06-13 18:03 ` [PATCH 4/5] reset: zynq: " Paul Gortmaker
2016-06-13 19:15   ` Moritz Fischer
2016-06-14  5:57   ` Michal Simek
2016-06-13 18:03 ` [PATCH 5/5] reset: lpc18xx: " Paul Gortmaker
2016-09-05 22:25 ` [PATCH 0/5] reset: make non-modular drivers really non modular Paul Gortmaker
2016-10-22 21:48 ` Paul Gortmaker
2016-10-24  8:56   ` Philipp Zabel [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=1477299405.2446.9.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=antoine.tenart@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manabian@gmail.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=michal.simek@xilinx.com \
    --cc=moritz.fischer@ettus.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=s.trumtrar@pengutronix.de \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=soren.brinkmann@xilinx.com \
    --cc=yamada.masahiro@socionext.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

Powered by JetHome