All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Bernard Blackham <bernard@blackham.com.au>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Address lots of pending pm_message_t changes
Date: Tue, 15 Feb 2005 00:41:52 +0100	[thread overview]
Message-ID: <20050214234151.GA2134@elf.ucw.cz> (raw)
In-Reply-To: <1108418990.12611.86.camel@desktop.cunningham.myip.net.au>

Hi!

> > > > > Andrew, if you get one big patch doing only type-safety (u32 ->
> > > > >  pm_message_t, no code changes), would you still take it this late? I
> > > > >  promise it is not going to break anything... It would help merge after
> > > > >  2.6.11 quite a lot...
> > > > 
> > > > Problem is, such a megapatch causes grief for all those people who maintain
> > > > their own trees.  It would be best, please, to split it into 10-20 bits and
> > > > send the USB parts to Greg and the SCSI bits to James, etc.
> > > 
> > > Okay; I can do that if everyone is happy with the thing as a whole.
> > > Andrew, can I get your answer on Pavel's question - shall I just include
> > > the u32->pm_message_t part?
> > 
> > Yes, I believe it is too late to do anything than u32->pm_message_t
> > conversion that changes no code...
> 
> I guess I'm wrong then - I thought the other changes avoided compilation
> errors.

Well, yes, if you switch pm_message_t into struct. But we are not yet
ready to do that... it is going to be typedefed to u32 for 2.6.11...

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2005-02-14 23:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14  5:43 PATCH: Address lots of pending pm_message_t changes Nigel Cunningham
2005-02-14 21:34 ` Pavel Machek
2005-02-14 21:46   ` Andrew Morton
2005-02-14 21:57     ` Nigel Cunningham
2005-02-14 22:04       ` Pavel Machek
2005-02-14 22:09         ` Nigel Cunningham
2005-02-14 23:41           ` Pavel Machek [this message]
2005-02-15  0:15             ` Nigel Cunningham
2005-02-15  0:15               ` Pavel Machek
2005-02-15  0:21                 ` Nigel Cunningham
2005-02-15  1:13               ` Bernard Blackham
2005-02-15  0:31     ` Fix pm_message_t in generic code [was Re: PATCH: Address lots of pending pm_message_t changes] Pavel Machek
2005-02-15  0:46       ` Nigel Cunningham
2005-02-15  0:39     ` Fix u32 vs. pm_message_t in USB " Pavel Machek
2005-02-17 23:40       ` Greg KH
2005-02-28  1:24         ` Pavel Machek
2005-02-15  0:41     ` Fix u32 vs. pm_message_t confusion in OSS Pavel Machek
2005-02-15  0:46     ` Fix u32 vs. pm_message_t confusion in PCMCIA Pavel Machek
2005-02-15  0:47     ` FIx u32 vs. pm_message_t confusion in firewire Pavel Machek
2005-02-15 22:12       ` Jody McIntyre
2005-02-15  0:51     ` Fix u32 vs. pm_message_t in network device drivers Pavel Machek
2005-02-15  0:54     ` Fix u32 vs. pm_message_t confusion in framebuffers Pavel Machek
2005-02-15  0:55     ` Fix u32 vs. pm_message_t in i8042.c Pavel Machek
2005-02-15 13:10       ` Vojtech Pavlik
2005-02-15  0:57     ` Fix u32 vs. pm_message_t confusion in MMC Pavel Machek
2005-02-15  0:58     ` Fix u32 vs. pm_message_t confusion in serials Pavel Machek
2005-02-15  1:00     ` Fix u32 vs. pm_message_t in macintosh Pavel Machek
2005-02-15  1:00     ` Fix u32 vs. pm_message_t confusion in bttv Pavel Machek
2005-02-15  1:01     ` Fix u32 vs. pm_message_t confusion in AGP Pavel Machek
2005-02-14 21:46 ` PATCH: Address lots of pending pm_message_t changes 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=20050214234151.GA2134@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=bernard@blackham.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    --cc=torvalds@osdl.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.