All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Prepping a bugfix push
Date: Fri, 4 Dec 2009 09:10:44 -0500	[thread overview]
Message-ID: <20091204141044.GA22585@phenom.dumpdata.com> (raw)
In-Reply-To: <1259923510.23698.15427.camel@zakaz.uk.xensource.com>

On Fri, Dec 04, 2009 at 10:45:10AM +0000, Ian Campbell wrote:
> On Thu, 2009-12-03 at 19:26 +0000, Jeremy Fitzhardinge wrote:
> > I'm preparing a general bugfix push for Linus, targeted at both current
> > linux-2.6.git and stable.  The list of patches I have lined up (in the
> > "bugfix" branch) are below.  Is there anything I've overlooked?  Are
> > there any patches I've forgotten to apply altogether?

How about those three fb-defio patches? Jaya said he would happy
if you posted them to Linus.

  reply	other threads:[~2009-12-04 14:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 19:26 Prepping a bugfix push Jeremy Fitzhardinge
2009-12-03 19:35 ` Brendan Cully
2009-12-03 19:38   ` Jeremy Fitzhardinge
2009-12-03 23:22   ` Jeremy Fitzhardinge
2009-12-04  0:24     ` Brendan Cully
2009-12-04  1:10       ` Jeremy Fitzhardinge
2009-12-04  4:29         ` Brendan Cully
2009-12-04  7:46         ` Ian Campbell
2009-12-04 15:50           ` Ian Campbell
2009-12-04 16:37             ` Jeremy Fitzhardinge
2009-12-04 16:56               ` Ian Campbell
2009-12-05  0:05                 ` Jeremy Fitzhardinge
2009-12-04 17:01               ` Brendan Cully
2009-12-04 17:12                 ` Jeremy Fitzhardinge
2009-12-04 10:45 ` Ian Campbell
2009-12-04 14:10   ` Konrad Rzeszutek Wilk [this message]
2009-12-04 16:18     ` Jeremy Fitzhardinge

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=20091204141044.GA22585@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=jeremy@goop.org \
    --cc=pbonzini@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /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.