From: James Hogan <james.hogan@imgtec.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, "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)
Date: Mon, 28 Jan 2013 22:30:45 +0000 [thread overview]
Message-ID: <20130128223045.GA16250@balrog> (raw)
In-Reply-To: <CA+icZUUHFFB6j-igX-Ec+6ZT2yvGakRd+HNVru1VUAxPXby_Lg@mail.gmail.com>
On Mon, Jan 28, 2013 at 11:06:11PM +0100, Sedat Dilek wrote:
> I don't see that git-bisect session as a time of waste, but two hints:
>
> 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"
> ...').
Okay, thanks for the tips. I'll be sure to do this in future.
Cheers
James
prev parent reply other threads:[~2013-01-28 22:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 11:10 linux-next: Tree for Jan 25 (BROKEN suspend) Sedat Dilek
2013-01-26 12:05 ` Sedat Dilek
2013-01-26 13:25 ` Rafael J. Wysocki
2013-01-26 13:24 ` Sedat Dilek
2013-01-26 14:33 ` Sedat Dilek
2013-01-26 15:05 ` Sedat Dilek
2013-01-26 18:27 ` Sedat Dilek
2013-01-26 21:49 ` Rafael J. Wysocki
2013-01-27 13:01 ` Sedat Dilek
2013-01-28 19:28 ` Tejun Heo
2013-01-28 22:06 ` Sedat Dilek
2013-01-28 22:08 ` Tejun Heo
2013-01-28 22:18 ` Sedat Dilek
2013-01-28 22:30 ` James Hogan [this message]
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=20130128223045.GA16250@balrog \
--to=james.hogan@imgtec.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=sasha.levin@oracle.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.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.