ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: josh@joshtriplett.org
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Reviewing new API/ABI
Date: Tue, 6 May 2014 14:00:07 -0700	[thread overview]
Message-ID: <20140506210007.GA21791@cloud> (raw)
In-Reply-To: <20140506164201.69611e7d@gandalf.local.home>

On Tue, May 06, 2014 at 04:42:01PM -0400, Steven Rostedt wrote:
> On Tue, 6 May 2014 13:34:26 -0700
> Josh Triplett <josh@joshtriplett.org> wrote:
> 
> > On Tue, May 06, 2014 at 04:07:40PM -0400, Steven Rostedt wrote:
> > > On Tue, 6 May 2014 12:00:24 -0700
> > > Greg KH <greg@kroah.com> wrote:
> > > 
> > > 
> > > > We do have linux-api, which should be cc:ed for new api additions.  But
> > > > it usually isn't :(
> > > 
> > > That's the first I've heard of that list. Maybe that's the reason it
> > > hasn't been cc'd much. Hard to Cc lists that you don't know about.
> > > 
> > > /me goes to look in MAINTAINERS for linux-api mailing list. Nope, not
> > > there.
> > 
> > Here's a patch:
> > 
> > ---8<---
> > >From 424c7365ed5ed64190a1d08fe30c8e86832368b4 Mon Sep 17 00:00:00 2001
> > From: Josh Triplett <josh@joshtriplett.org>
> > Date: Tue, 6 May 2014 13:20:25 -0700
> > Subject: [PATCH] MAINTAINERS: Add linux-api for review of API/ABI changes
> > 
> > This makes it more likely that patch submitters will CC API/ABI changes
> > to the linux-api list, and tools like get_maintainer.pl will do so
> > automatically.
> > 
> 
> Although patches need to go to LKML.
> 
> Acked-by: Steven Rostedt <rostedt@goodmis.org>

Resent to LKML.

  reply	other threads:[~2014-05-06 21:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 17:45 Andy Lutomirski
2014-05-06 17:58 ` josh
2014-05-06 19:12   ` Shuah Khan
2014-05-06 19:16     ` Andy Lutomirski
2014-05-06 19:37       ` Shuah Khan
2014-05-06 19:21   ` Johannes Berg
2014-05-06 19:43     ` Andy Lutomirski
2014-05-06 19:48       ` Johannes Berg
2014-05-06 19:51         ` Andy Lutomirski
2014-05-06 19:45     ` josh
2014-05-06 20:10     ` Daniel Vetter
2014-05-06 20:13       ` Andy Lutomirski
2014-05-07 10:12     ` Laurent Pinchart
2014-05-07 12:36       ` Daniel Vetter
2014-05-07 13:30         ` Laurent Pinchart
2014-05-07 13:50           ` Hans Verkuil
2014-05-12 14:15         ` Wolfram Sang
2014-05-07 17:48   ` Michael Kerrisk (man-pages)
2014-05-06 19:00 ` Greg KH
2014-05-06 20:07   ` Steven Rostedt
2014-05-06 20:34     ` Josh Triplett
2014-05-06 20:42       ` Steven Rostedt
2014-05-06 21:00         ` josh [this message]
2014-05-07 11:48       ` Jiri Kosina
2014-05-08  6:35         ` Li Zefan
2014-05-12  6:37           ` Jiri Kosina
2014-05-07  6:27   ` Michael Kerrisk (man-pages)
2014-05-06 19:57 ` Dan Carpenter
2014-05-08 18:15   ` Randy Dunlap
2014-05-09 11:33 ` Jeff Layton
2014-05-09 11:50   ` Michael Kerrisk (man-pages)

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=20140506210007.GA21791@cloud \
    --to=josh@joshtriplett.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rostedt@goodmis.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