From: Christoph Hellwig <hch@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: emilne@redhat.com, James Bottomley <jbottomley@parallels.com>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
DL-MPTFusionLinux@lsi.com, MPT-FusionLinux.pdl@avagotech.com
Subject: Re: [PATCH] fusion: fix excess parameter kernel-doc warning
Date: Wed, 27 Aug 2014 17:55:41 -0700 [thread overview]
Message-ID: <20140828005541.GA20009@infradead.org> (raw)
In-Reply-To: <53FE6E0C.5040101@infradead.org>
On Wed, Aug 27, 2014 at 04:47:24PM -0700, Randy Dunlap wrote:
> > Goes with commit c9834c70efbaaa1461ec04289d97a842244fb294.
> >
> > Reviewed-by: Ewan D. Milne <emilne@redhat.com>
>
> Christoph, did you pick up this patch or should I merge it
> with my documentation patches?
I did as mentioned in my reply to your other patch.
next prev parent reply other threads:[~2014-08-28 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 21:15 [PATCH] fusion: fix excess parameter kernel-doc warning Randy Dunlap
2014-08-18 17:07 ` Ewan Milne
2014-08-27 23:47 ` Randy Dunlap
2014-08-28 0:55 ` Christoph Hellwig [this message]
2014-08-28 6:28 ` Randy Dunlap
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=20140828005541.GA20009@infradead.org \
--to=hch@infradead.org \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=MPT-FusionLinux.pdl@avagotech.com \
--cc=emilne@redhat.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@infradead.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 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).