All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bhanu Prakash Gollapudi <bprakash@broadcom.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Joe Perches <joe@perches.com>
Subject: Re: [PATCH] bnx2fc: use kthread_create_on_node
Date: Wed, 30 May 2012 12:30:11 +0400	[thread overview]
Message-ID: <1338366611.3229.8.camel@dabdike> (raw)
In-Reply-To: <4FC56943.6000304@broadcom.com>

On Tue, 2012-05-29 at 17:26 -0700, Bhanu Prakash Gollapudi wrote:
> On 7/29/2011 12:22 PM, Bhanu Prakash Gollapudi wrote:
> > On 7/29/2011 12:06 AM, Eric Dumazet wrote:
> >> Since bnx2fc_percpu_thread_create() creates percpu kthread, it makes
> >> sense to use kthread_create_on_node() to get proper NUMA affinity for
> >> kthread stack.
> >>
> >> Signed-off-by: Eric Dumazet<eric.dumazet@gmail.com>
> >> CC: "James E.J. Bottomley"<JBottomley@parallels.com>
> >
> > Thanks Eric.
> >
> > Acked-by: Bhanu Prakash Gollapudi<bprakash@broadcom.com>
> 
> James, I found a couple of old patches that were not applied, this being 
> one and the other - http://marc.info/?l=linux-scsi&m=132561632116410&w=2.
> 
> Please let me know if you want the patches to be resubmitted, as they 
> are a bit old now.

Yes, please.  And for future reference, if I ever miss anything you want
in, just fold it into your internal queue and resend for your next batch
(with the appropriate signoffs).

Thanks,

James



      parent reply	other threads:[~2012-05-30  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29  7:06 [PATCH] bnx2fc: use kthread_create_on_node Eric Dumazet
2011-07-29 19:22 ` Bhanu Prakash Gollapudi
2012-05-30  0:26   ` Bhanu Prakash Gollapudi
2012-05-30  0:33     ` Joe Perches
2012-05-30  8:30     ` James Bottomley [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=1338366611.3229.8.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=bprakash@broadcom.com \
    --cc=eric.dumazet@gmail.com \
    --cc=joe@perches.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.