All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Ball <cjb@laptop.org>
Cc: Matt Fleming <matt@console-pimps.org>,
	Linus Walleij <linus.ml.walleij@gmail.com>,
	linux-mmc@vger.kernel.org
Subject: Re: MMC workflow (was Re: [PATCH] mmc: MMC 4.4 DDR support)
Date: Mon, 23 Aug 2010 15:05:21 -0700	[thread overview]
Message-ID: <20100823150521.e6629a85.akpm@linux-foundation.org> (raw)
In-Reply-To: <m34oelq9zb.fsf_-_@pullcord.laptop.org>

On Mon, 23 Aug 2010 17:45:28 -0400
Chris Ball <cjb@laptop.org> wrote:

> Hi,
> 
>    > It's possible Andrew has a reason that hasn't been picked up yet.
>    > 
>    > Maybe what we really need is to get patchwork setup for the
>    > linux-mmc list? Other subsystem maintainers swear by it. That
>    > way, it'd be much harder for patches to go unnoticed.
> 
> Sounds good -- if no-one objects, I'll send e-mail to ftpadmin@k.o
> tomorrow asking for linux-mmc@ to be added to patchwork.k.o.
> 
> Andrew, how do you feel about MMC at the moment?  It seems like we
> could mostly use more people reviewing patches, but do you think it'd
> also help to have submitted patches go into a -next tree for testing?
> Would you like to have someone else track down which patches got held
> up along the way and should be revisited, or is that something you're
> already doing?
> 

I'm basically acting as a stopgap patch monkey until a real maintainer
comes along.

I'll happily read the patches myself but do very much like to see that
someone with mmc-specific experience has taken a look at them as well.

So for me, review really really helps.  The only other issue I have is
that I don't read the list often enough, so please do add me to cc on
replies if I was missed out on.

I actually "maintain" well over 100 "subsystems" in this manner[*]. 
Really I should be in MAINTAINERS for a lot of these so I get cc'ed
more reliably on those oddball once-off fixes.  But usually they're cc'ed
to lkml so I do see them.


[*]:

	grep '^# ' series

is below.  I have headings for "other maintainers trees" and headings
for "trees I maintain" and headings for random junk which probably
shouldn't be there any more.  That series file has been checked in 19194
times since Dec 2002.  I should get out more.


# 2.6.36
# me:
# 2.6.33, early
# acpi
# platform drivers
# x86
# alsa
# kgdb
# kmemcheck
# agp
# arm
# audit
# avr32
# btrfs
# ceph
# cifs
# cpufreq
# dm
# dmar (dwmw2)
# dma (Dan)
# dma-debug (Joerg Roedel <joerg.roedel@amd.com>)
# jfs
# pcmcia
# powerpc
# driver core
# dnotify
# drm
# dvb
# ecryptfs
# fscache
# fsnotify
# hpet
# i2c
# iommu
# irqs
# gfs
# hid
# hwpoison
# time
# ntp
# ia64
# ieee1394
# infiniband
# input
# kbuild
# kvm
# kvm/ia64
# lblnet
# leds
# libata
# pata
# ide
# m32r
# mfd
# microblaze
# async-tx
# mips
# mqueue
# mtd
# nfsd
# ntfs
# score
# spi
# squashfs
# ubi
# ubifs
# udf
# uwb
# connector (davem)
# atm
# wan
# irda
# i4l
# net
# netdev
# netfilter
# backlight
# battery
# blackfin
# bluetooth
# debugobjects
# ext4
# nfs
# ocfs2
# parisc
# security
# serial
# udf
# pci
# md
# perf
# regulator
# s390
# sched
# tejun stuff
# genirq
# lockdep
# fastboot
# rcu
# ftrace
# sh
# scsi
# block
# sparc
# staging
# uio
# usb
# v9fs
# vfs
# watchdog
# wireless
# xfs
# crypto
# xtensa
# rusty
# slab
# tty
# mm
# mmend
# security
# frv
# pagemap
# gigaset
# nommu
# sh
# h8/300
# alpha
# CPU hotplug
# power management
# m32r
# m68k
# mn10300
# cpuidle
# cris
# floppy
# uml
# v850
# Misc
# miscend
# drivers/misc
# *bmp085*: fold
# core kernel
# miscdev
# printk
# get_maintainer
# MAINTAINERS
# lib
# bkl removal
# sgi-xpc
# compat
# firmware
# mmc
# sdhci-*: perf regression (Albert Herranz <albert_herranz@yahoo.es>)
# checkpatch
# crc
# poll select
# epoll
# hwmon
# smm665: fold
# oss
# binfmt
# warn
# list
# topology:
# swiotlb
# kallsyms
# ramfs
# rwsem
# initramfs
# ncpfs
# dmi
# oprofile
# vt
# kprobes
# i2o
# xen
# autofs
# smbfs
# rtc
# gpio
# fbdev
# auxdisplay
# devmem
# pnp
# pnpbios
# pipe
# telephony
# minix
# ext2
# ext3
# befs
# isofs
# codafs
# nilfs
# hfs
# hfsplus
# ufs
# reiserfs
# hpfs
# hppfs
# fat
# quota
# documentation
# cgroups
# devcgroup
# memcgroup
# devscgroup
# cpusets
# ptrace
# utrace
# signals
# pgrp
# kmod
# coredump
# exit
# proc
# fork
# exec
# wait
# workqueues
# kthread
# cpu hotplug
# kdump
# idr
# ipc
# ipmi
# pty
# elf
# flat
# char
# hw_random
# drivers/misc
# partitions
# rapidio
# rbu
# keys
# sysctl
# pid management
# pidns
# userns
# edd
# nbd
# ioctl
# atmel
# aoe
# markers
# namespaces
# accounting
# taskstats
# random
# fuse
# futex
# edac
# gcov
# loop
# dma-mapping
# propagate these:
# adfs
# afs
# affs
# bfs
# panic
# parport
# pps
# memstick
# w1
# c2
# ramdisk
# kexec
# mmtimer
# ramzswap
# sysvfs
# cachefiles fs-cache
# markup_oops
# relayfs:
# aio
# dio
# omfs
# uv
# gru
# kfifo
# radix-tree
# resource
# ssb
# genclk
# cpualloc
# devpts
# byteorder
# unaligned
# cramfs
# ramoops
# ramzswap
# romfs
# freeze feature
# async
# vlynq
# qnx4
# static
# decompress
# ibft
# inflate deflate
# slow-work
# lkdtm
# lzo
# end
# debug stuff


  reply	other threads:[~2010-08-23 22:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09  6:59 [PATCH] mmc: MMC 4.4 DDR support Hanumath Prasad
2010-07-09  6:59 ` Hanumath Prasad
2010-07-10  5:28 ` Kyungmin Park
2010-07-10  5:29   ` Kyungmin Park
     [not found]   ` <81C3A93C17462B4BBD7E272753C10579169F9BD429@EXDCVYMBSTM005.EQ1STM.local>
2010-07-13  1:14     ` Kyungmin Park
2010-08-21 22:30 ` Linus Walleij
2010-08-21 22:37   ` Chris Ball
2010-08-23  7:21     ` Linus Walleij
2010-08-23 20:48     ` Matt Fleming
2010-08-23 21:28       ` Andrew Morton
2010-08-24 10:30         ` Adrian Hunter
2010-08-24 10:30           ` Adrian Hunter
2010-09-14 11:21           ` Chris Ball
2010-09-14 11:21             ` Chris Ball
2010-09-15  9:32             ` Ghorai, Sukumar
2010-09-15  9:32               ` Ghorai, Sukumar
2010-09-20  4:34             ` Ghorai, Sukumar
2010-09-20  4:34               ` Ghorai, Sukumar
2010-09-22  2:20               ` Chris Ball
2010-09-22  2:20                 ` Chris Ball
2010-09-30  8:06                 ` zhangfei gao
2010-09-30  8:06                   ` zhangfei gao
2010-09-30 22:30           ` Chris Ball
2010-09-30 22:30             ` Chris Ball
2010-08-23 21:45       ` MMC workflow (was Re: [PATCH] mmc: MMC 4.4 DDR support) Chris Ball
2010-08-23 22:05         ` Andrew Morton [this message]
2010-09-14  0:33         ` Chris Ball
2010-09-14  6:26           ` Wolfram Sang
2010-09-30 22:29 ` [PATCH] mmc: MMC 4.4 DDR support Chris Ball

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=20100823150521.e6629a85.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cjb@laptop.org \
    --cc=linus.ml.walleij@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matt@console-pimps.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.