public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: mathieu.poirier@linaro.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
	Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
	unsik Kim <donari75@gmail.com>
Subject: Re: [PATCH 0/6] drivers: randconfig patches for kernel 3.5
Date: Sat, 9 Jun 2012 00:13:27 +0000	[thread overview]
Message-ID: <201206090013.27149.arnd@arndb.de> (raw)
In-Reply-To: <1339194280-27475-1-git-send-email-mathieu.poirier@linaro.org>

On Friday 08 June 2012, mathieu.poirier@linaro.org wrote:
> From: Mathieu Poirier <mathieu.poirier@linaro.org>
> 
> These patches fix miscellaneous problems when working
> with make randconfig.  They were discovered on kernel
> 3.1-rc4 and sent out during the 3.4 cycle but were not
> ack'ed.  
> 
> Sending out again for completeness.

Hi Mathieu,

I just realized that most of these are for the same subsystem
(framebuffer), so you should have kept the respective mailing list
and maintainer on Cc (added now). 

The mg_disk driver is not listed in the MAINTAINERS file but
has an author email listed in the file itself.

I can take the mg_disk patch into the arm-soc tree as a fix,
but I'd prefer the other patches to go through the framebuffer
tree.

	Arnd

> Arnd Bergmann (6):
>   drivers/video: use correct __devexit_p annotation
>   mg_disk: use readb/writeb instead of inb/outb
>   video/ili9320: do not mark exported functions __devexit
>   video/console: automatically select a font
>   drivers/savagefb: use mdelay instead of udelay
>   drivers/tosa: driver needs I2C and SPI to compile
> 
>  drivers/block/mg_disk.c                |   78 ++++++++++++++++----------------
>  drivers/video/backlight/Kconfig        |    2 +-
>  drivers/video/backlight/ili9320.c      |    2 +-
>  drivers/video/broadsheetfb.c           |    2 +-
>  drivers/video/console/Kconfig          |   14 ++++++
>  drivers/video/mbx/mbxfb.c              |    2 +-
>  drivers/video/savage/savagefb_driver.c |   10 ++--
>  7 files changed, 62 insertions(+), 48 deletions(-)

  parent reply	other threads:[~2012-06-09  0:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 22:24 [PATCH 0/6] drivers: randconfig patches for kernel 3.5 mathieu.poirier
2012-06-08 22:24 ` [PATCH RESEND 1/6] drivers/video: use correct __devexit_p annotation mathieu.poirier
2012-06-08 22:24 ` [PATCH RESEND 2/6] mg_disk: use readb/writeb instead of inb/outb mathieu.poirier
2012-06-08 22:24 ` [PATCH RESEND 3/6] video/ili9320: do not mark exported functions __devexit mathieu.poirier
2012-06-08 22:24 ` [PATCH RESEND 4/6] video/console: automatically select a font mathieu.poirier
2012-06-08 22:24 ` [PATCH RESEND 5/6] drivers/savagefb: use mdelay instead of udelay mathieu.poirier
2012-06-08 22:24 ` [PATCH RESEND 6/6] drivers/tosa: driver needs I2C and SPI to compile mathieu.poirier
2012-06-09  0:13 ` Arnd Bergmann [this message]
2012-06-09 12:57   ` [PATCH 0/6] drivers: randconfig patches for kernel 3.5 Florian Tobias Schandinat
2012-06-09 21:28     ` Arnd Bergmann

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=201206090013.27149.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=FlorianSchandinat@gmx.de \
    --cc=donari75@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.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