From: Michael Ellerman <michael@ellerman.id.au>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iSeries: Remove unused mf_getSrcHistory function and caller.
Date: Fri, 19 Nov 2010 08:57:50 +1100 [thread overview]
Message-ID: <1290117470.29105.9.camel@concordia> (raw)
In-Reply-To: <alpine.LNX.2.00.1011182044490.3651@swampdragon.chaosbits.net>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
On Thu, 2010-11-18 at 20:45 +0100, Jesper Juhl wrote:
> On Fri, 5 Nov 2010, Jesper Juhl wrote:
> >
> > static int mf_src_proc_open(struct inode *inode, struct file *file)
> PING.
>
> Is this going to get merged somewhere or is there a problem?
Yes, no.
It won't get lost:
http://patchwork.ozlabs.org/patch/70201/
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-11-18 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 17:20 [PATCH] iSeries: Don't leak if allocations fail in mf_getSrcHistory Jesper Juhl
2010-11-01 11:10 ` Michael Ellerman
2010-11-01 20:10 ` Stephen Rothwell
2010-11-01 20:06 ` [PATCH] iSeries: Remove unused mf_getSrcHistory function Jesper Juhl
2010-11-01 21:26 ` Stephen Rothwell
2010-11-01 21:20 ` Jesper Juhl
2010-11-02 0:20 ` Michael Ellerman
2010-11-04 23:29 ` [PATCH v2] iSeries: Remove unused mf_getSrcHistory function and caller Jesper Juhl
2010-11-18 19:45 ` Jesper Juhl
2010-11-18 21:57 ` Michael Ellerman [this message]
2010-11-18 21:51 ` Jesper Juhl
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=1290117470.29105.9.camel@concordia \
--to=michael@ellerman.id.au \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).