From: Randy Dunlap <randy.dunlap@oracle.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH 0/7] lpfc 8.3.1 : Update lpfc to revision 8.3.1
Date: Wed, 13 May 2009 12:22:51 -0700 [thread overview]
Message-ID: <4A0B1E0B.40108@oracle.com> (raw)
In-Reply-To: <1239058022.2344.19.camel@ogier>
James Smart wrote:
> Update lpfc driver to revision 8.3.1
>
> Includes the following changes :
> - A set of 5 patches to update kdoc headers. These were posted earlier
> but have not been picked up yet.
> - A set of miscellaneous fixes/changes, all small in nature. Includes
> Null pointer fixes, sparse fixes, and some feature updates.
> - Update driver version to 8.3.0
>
> -- james s
James (Bottomley),
Can we get this patchset merged for 2.6.30?
It fixes http://bugzilla.kernel.org/show_bug.cgi?id=13242
which I am also running into quite often.
--
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
prev parent reply other threads:[~2009-05-13 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 22:47 [PATCH 0/7] lpfc 8.3.1 : Update lpfc to revision 8.3.1 James Smart
2009-05-13 19:22 ` Randy Dunlap [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=4A0B1E0B.40108@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=James.Smart@Emulex.Com \
--cc=linux-scsi@vger.kernel.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