From: Greg KH <gregkh@linuxfoundation.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Unique commit-id for "mm: compaction: [P,p]artially revert capture of suitable high-order page"
Date: Mon, 14 Jan 2013 09:01:34 -0800 [thread overview]
Message-ID: <20130114170134.GA26655@kroah.com> (raw)
In-Reply-To: <20130114130911.GQ13304@suse.de>
On Mon, Jan 14, 2013 at 01:09:11PM +0000, Mel Gorman wrote:
> On Mon, Jan 14, 2013 at 12:27:20PM +0100, Sedat Dilek wrote:
> > On Mon, Jan 14, 2013 at 11:36 AM, Mel Gorman <mgorman@suse.de> wrote:
> > > On Sun, Jan 13, 2013 at 05:12:45PM +0100, Sedat Dilek wrote:
> > >> Hi Linus,
> > >>
> > >> I see two different commit-id for an identical patch (only subject
> > >> line differs).
> > >> [1] seems to be applied directly and [2] came with a merge of akpm-fixes.
> > >> What is in case of backports for -stable kernels?
> > >
> > > I do not expect it to matter. I was going to use
> > > 8fb74b9fb2b182d54beee592350d9ea1f325917a as the commit ID whenever I got
> > > the complaint mail from Greg's tools about a 3.7 merge failure. The 3.7.2
> > > backport looks like this.
> > >
> >
> > Oh cool and thanks!
> > Are you planning to resend this backport-patch to the lists w/ a "3.7"
> > (or for-3.7) in the commit-subject?
> >
>
> Yes, when I get the reject mail from Greg's tools.
You should have that rejection email now :)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Unique commit-id for "mm: compaction: [P,p]artially revert capture of suitable high-order page"
Date: Mon, 14 Jan 2013 09:01:34 -0800 [thread overview]
Message-ID: <20130114170134.GA26655@kroah.com> (raw)
In-Reply-To: <20130114130911.GQ13304@suse.de>
On Mon, Jan 14, 2013 at 01:09:11PM +0000, Mel Gorman wrote:
> On Mon, Jan 14, 2013 at 12:27:20PM +0100, Sedat Dilek wrote:
> > On Mon, Jan 14, 2013 at 11:36 AM, Mel Gorman <mgorman@suse.de> wrote:
> > > On Sun, Jan 13, 2013 at 05:12:45PM +0100, Sedat Dilek wrote:
> > >> Hi Linus,
> > >>
> > >> I see two different commit-id for an identical patch (only subject
> > >> line differs).
> > >> [1] seems to be applied directly and [2] came with a merge of akpm-fixes.
> > >> What is in case of backports for -stable kernels?
> > >
> > > I do not expect it to matter. I was going to use
> > > 8fb74b9fb2b182d54beee592350d9ea1f325917a as the commit ID whenever I got
> > > the complaint mail from Greg's tools about a 3.7 merge failure. The 3.7.2
> > > backport looks like this.
> > >
> >
> > Oh cool and thanks!
> > Are you planning to resend this backport-patch to the lists w/ a "3.7"
> > (or for-3.7) in the commit-subject?
> >
>
> Yes, when I get the reject mail from Greg's tools.
You should have that rejection email now :)
next prev parent reply other threads:[~2013-01-14 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 16:12 Unique commit-id for "mm: compaction: [P,p]artially revert capture of suitable high-order page" Sedat Dilek
2013-01-13 16:12 ` Sedat Dilek
2013-01-14 10:36 ` Mel Gorman
2013-01-14 10:36 ` Mel Gorman
2013-01-14 11:27 ` Sedat Dilek
2013-01-14 11:27 ` Sedat Dilek
2013-01-14 13:09 ` Mel Gorman
2013-01-14 13:09 ` Mel Gorman
2013-01-14 17:01 ` Greg KH [this message]
2013-01-14 17:01 ` Greg KH
2013-01-14 19:20 ` Mel Gorman
2013-01-14 19:20 ` Mel Gorman
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=20130114170134.GA26655@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=sedat.dilek@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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.