All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Robin Holt <holt@sgi.com>
Subject: How should I proceed to get commit 891348c to 3.0.y?
Date: Thu, 24 Jan 2013 09:28:51 -0600	[thread overview]
Message-ID: <20130124152851.GF3460@sgi.com> (raw)


I missed the email from 12/31 indicating commit 891348c was pulled from
the 3.0.y stable tree due to a build breakage.

That commit requires the enum defined in traps.h by commit c940826.  That,
in turn depends on commit 228bdaa95f which depends upon earlier commits.

How should I proceed?  Should I give you a patch that uses the constants
in xpc_main.c? Should I add a patch which just pulls the enum portion of
commit c940826 into traps.h? Any other direction you think this should go?

Thanks,
Robin

             reply	other threads:[~2013-01-24 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 15:28 Robin Holt [this message]
2013-01-24 18:15 ` How should I proceed to get commit 891348c to 3.0.y? Greg KH
2013-01-24 18:30   ` Robin Holt
2013-01-24 20:00     ` Greg KH
2013-01-24 20:14       ` Robin Holt
2013-01-24 20:50         ` Greg KH
2013-01-24 20:52           ` Robin Holt

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=20130124152851.GF3460@sgi.com \
    --to=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.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.