public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@suse.cz>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: fix-u32-vs-pm_message_t-in-usb
Date: Fri, 18 Mar 2005 15:53:13 -0800	[thread overview]
Message-ID: <20050318155313.60a4670f.akpm@osdl.org> (raw)
In-Reply-To: <20050318234440.GF24449@elf.ucw.cz>

Pavel Machek <pavel@suse.cz> wrote:
>
> > Care to just rediff off of 2.6.12-rc1?  Then we can hopefully get these
>  > changes in :)
> 
>  I can do the rediff tommorow. I just hope there are not some other
>  changis waiting in -mm to spoil this ;-).

I have a boatload of these darn pm_message_t patches floating about.  I
don't know if they depend on Greg's stuff or not.

Should I just hose them at him?

fix-pm_message_t-in-generic-code.patch
fix-u32-vs-pm_message_t-in-usb.patch
fix-u32-vs-pm_message_t-in-usb-fix.patch
more-pm_message_t-fixes.patch
fix-u32-vs-pm_message_t-confusion-in-oss.patch
fix-u32-vs-pm_message_t-confusion-in-pcmcia.patch
fix-u32-vs-pm_message_t-confusion-in-framebuffers.patch
fix-u32-vs-pm_message_t-confusion-in-mmc.patch
fix-u32-vs-pm_message_t-confusion-in-serials.patch
fix-u32-vs-pm_message_t-in-macintosh.patch
fix-u32-vs-pm_message_t-confusion-in-agp.patch


  reply	other threads:[~2005-03-18 23:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050310223353.47601d54.akpm@osdl.org>
2005-03-11 13:08 ` fix-u32-vs-pm_message_t-in-usb Pavel Machek
2005-03-18 21:43   ` fix-u32-vs-pm_message_t-in-usb Greg KH
2005-03-18 23:44     ` fix-u32-vs-pm_message_t-in-usb Pavel Machek
2005-03-18 23:53       ` Andrew Morton [this message]
2005-03-19  0:00         ` fix-u32-vs-pm_message_t-in-usb Pavel Machek
2005-03-19  0:28         ` fix-u32-vs-pm_message_t-in-usb Pavel Machek
2005-03-11 13:10 ` fix-u32-vs-pm_message_t-in-usb Pavel Machek

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=20050318155313.60a4670f.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox