mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Benjamin Li" <benli@broadcom.com>
Cc: "Matthew Wilcox" <willy@linux.intel.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Linux Netdev List" <netdev@vger.kernel.org>,
	"Michael Chan" <mchan@broadcom.com>
Subject: Re: [PATCH] PCI: Add limits to VPD read/write lengths for Broadcom 5706S, 5708S
Date: Thu, 31 Jul 2008 12:41:05 -0700	[thread overview]
Message-ID: <200807311241.06209.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1217532284-7032-2-git-send-email-benli@broadcom.com>

On Thursday, July 31, 2008 12:24 pm Benjamin Li wrote:
> Reading beyond the valid VPD limit will hang the Broadcom
> 5706S, 5708S.  During the check we need to add the additionial
> 5706S and 5708S PCI ID's when limiting the read/write VPD length.
>
> Signed-off-by: Benjamin Li <benli@broadcom.com>

I already applied Eric's 5708S patch, can you re-diff against my for-linus 
branch (in a few minutes after it mirrors out) and resend?  And please cc 
stable@vger.kernel.org, since they'll want these crash fixes too.

Thanks,
Jesse

  parent reply	other threads:[~2008-07-31 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 18:27 [PATCH] PCI: Limit VPD length for Broadcom 5708S Eric Dumazet
2008-07-31 19:39 ` Jesse Barnes
     [not found] ` <1217532284-7032-1-git-send-email-benli@broadcom.com>
     [not found]   ` <1217532284-7032-2-git-send-email-benli@broadcom.com>
2008-07-31 19:41     ` Jesse Barnes [this message]
2008-10-27 22:27 ` Eric Dumazet
2008-10-28  3:26   ` Benjamin Li
2008-10-28  6:21     ` Eric Dumazet
2008-10-28  6:44       ` Yu Zhao
2008-10-28  8:38         ` Eric Dumazet
2008-10-30 16:14         ` Jesse Barnes
2008-11-03 22:37         ` Jesse Barnes
2008-10-28 16:25     ` Benjamin Li

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=200807311241.06209.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=benli@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=willy@linux.intel.com \
    /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
Powered by JetHome