public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	linux-arm-kernel@lists.infradead.org,
	Ludovic Desroches <ludovic.desroches@atmel.com>,
	Josh Wu <josh.wu@atmel.com>,
	linux-kernel@vger.kernel.org, mturquette@baylibre.com
Subject: Re: [PATCH] clk: at91: add generated clock driver
Date: Thu, 18 Jun 2015 17:11:52 +0200	[thread overview]
Message-ID: <1434640312.2385.112.camel@x220> (raw)
In-Reply-To: <20150618125918.GC27492@piout.net>

Hi Alexandre,

You know, I can't read Nicolas' mind, so I couldn't say from the patch
itself that it was not a silly mistake.

I also can't look into the future. I can however check lkml (at least
the few weeks of lkml I keep at hand) and see whether there's another
patch pending that would allow this driver to build.

Discussing those two disabilities doesn't require a (much broader)
discussion on how Atmel goes about their Linux business. At least, I
hope it doesn't, because I don't actually have an opinion in that
matter.

Thanks,


Paul Bolle


  parent reply	other threads:[~2015-06-18 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 13:23 [PATCH] clk: at91: add generated clock driver Nicolas Ferre
2015-06-18  7:12 ` Paul Bolle
2015-06-18  7:33   ` Boris Brezillon
2015-06-18  7:40     ` Nicolas Ferre
2015-06-18  7:54       ` Paul Bolle
2015-06-18 12:40         ` Nicolas Ferre
2015-06-18 14:46           ` Paul Bolle
2015-06-18 12:59         ` Alexandre Belloni
2015-06-18 13:28           ` Nicolas Ferre
2015-06-18 15:11           ` Paul Bolle [this message]
2015-06-18  7:44     ` Paul Bolle
2015-06-18 15:25 ` Boris Brezillon
2015-06-22 16:50   ` Nicolas Ferre

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=1434640312.2385.112.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=josh.wu@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=mturquette@baylibre.com \
    --cc=nicolas.ferre@atmel.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