From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755276Ab3A1WIw (ORCPT <rfc822;w@1wt.eu>);
	Mon, 28 Jan 2013 17:08:52 -0500
Received: from mail-qe0-f47.google.com ([209.85.128.47]:51181 "EHLO
	mail-qe0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754679Ab3A1WIv (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 28 Jan 2013 17:08:51 -0500
Date: Mon, 28 Jan 2013 14:08:44 -0800
From: Tejun Heo <tj@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Stephen Rothwell <sfr@canb.auug.org.au>,
        linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
        Linux PM List <linux-pm@lists.linux-foundation.org>,
        Linux ACPI <linux-acpi@vger.kernel.org>,
        Sasha Levin <sasha.levin@oracle.com>,
        James Hogan <james.hogan@imgtec.com>
Subject: Re: linux-next: Tree for Jan 25 (BROKEN suspend)
Message-ID: <20130128220844.GO22465@mtj.dyndns.org>
References: <CA+icZUW6LBSjpqK-eQUAt7R=kXCPRjFoi=z1UijaajrVAj=fEg@mail.gmail.com>
 <CA+icZUX=XdAJjWwx8P_y31JGW3GC+tdWuFhv2Ym-0OELGWGbDQ@mail.gmail.com>
 <CA+icZUX31SB3+NU8uXA9LH5KOHxgeHKZLcqWNhzUVhx5onk6qA@mail.gmail.com>
 <18624541.r6CtJttOWZ@vostro.rjw.lan>
 <CA+icZUX+o6kB9wXwpuJ8U49j+qHdx=DRq7p+_U1g+1fwGb-S6w@mail.gmail.com>
 <20130128192807.GF22465@mtj.dyndns.org>
 <CA+icZUUHFFB6j-igX-Ec+6ZT2yvGakRd+HNVru1VUAxPXby_Lg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+icZUUHFFB6j-igX-Ec+6ZT2yvGakRd+HNVru1VUAxPXby_Lg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hello, Sedat.

On Mon, Jan 28, 2013 at 11:06:11PM +0100, Sedat Dilek wrote:
> 1. People should sent their patches concerning especially Linux-Next
> fixes not only to LKML but also to <linux-next@vger.kernel.org> (if
> this is not known, pointing to James).
> 
> 2. These patches for Linux-Next should contain a "-next" in their
> subject-line (use 'git format-patch --subject-prefix="PATCH -next"
> ...').
> 
> Of course, I should have checked the MLs... but for me it was not
> clear what was the root cause (which subsystem to blame)... I had only
> some suspicions.

Yeah, there was no way for you guys to easily discover that the
problem has already been identified and fix pending.  I'll definitely
try to cc linux-next cc'd on patches which fix problems in -next.

Thanks a lot!

-- 
tejun