From: Eugene Surovegin <ebs@ebshome.net>
To: viro@ZenIV.linux.org.uk
Cc: linuxppc-dev@ozlabs.org, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] missed s/u32/pm_message_t/ in arch/ppc/syslib/ocp.c
Date: Mon, 5 Sep 2005 19:38:16 -0700 [thread overview]
Message-ID: <20050906023816.GB5512@gate.ebshome.net> (raw)
In-Reply-To: <20050906022733.GU5155@ZenIV.linux.org.uk>
On Tue, Sep 06, 2005 at 03:27:33AM +0100, viro@ZenIV.linux.org.uk wrote:
> On Mon, Sep 05, 2005 at 07:15:35PM -0700, Eugene Surovegin wrote:
>
> > Identical fix is already in -mm
>
> Then it really should go upstream; obvious fixes like that are not
> something that needs filtration...
Well, it's not up to me, really - I just follow our usual patch
submit procedure (i.e. send everything to Andrew). However, patch was
sent today in the morning (PDT), so I think Andrew will forward it to
Linus soon.
--
Eugene
prev parent reply other threads:[~2005-09-06 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 0:44 [PATCH] missed s/u32/pm_message_t/ in arch/ppc/syslib/ocp.c viro
2005-09-06 2:15 ` Eugene Surovegin
2005-09-06 2:27 ` viro
2005-09-06 2:38 ` Eugene Surovegin [this message]
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=20050906023816.GB5512@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=torvalds@osdl.org \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).