From: scameron@beardog.cce.hp.com
To: John Kacur <jkacur@redhat.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
linux-scsi@vger.kernel.org,
James Bottomley <jbottomley@parallels.com>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
Clark Williams <williams@redhat.com>,
scameron@beardog.cce.hp.com
Subject: Re: [PATCH] hpsa: fix warning with smp_processor_id() in preemptible
Date: Mon, 12 Aug 2013 08:58:45 -0500 [thread overview]
Message-ID: <20130812135845.GA15147@beardog.cce.hp.com> (raw)
In-Reply-To: <1290115203.630841.1376314412366.JavaMail.root@redhat.com>
On Mon, Aug 12, 2013 at 09:33:32AM -0400, John Kacur wrote:
>
>
> ----- Original Message -----
> > * John Kacur | 2013-07-26 16:42:30 [+0200]:
> >
> > >Signed-off-by: John Kacur <jkacur@redhat.com>
> > >Acked-by: Stephen <scameron@beardog.cce.hp.com>
> >
> > ping.
> >
> > I checked the branches for-next, scsi-fixes, fixes and misc at [0] and I
> > didn't see it. I'm going to take this for 3.10-rt but please don't lose
> > it on its way to Linus :)
> >
> > [0] git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git
>
>
> I hope it was clear to everyone that this patch was intended for upstream.
> It was discovered by running the real-time kernel, but it exposes a (minor) problem
> that should be fixed in the mainline kernel. Please apply it there Stephen, and
> push it upstream appropriately.
I don't have such pushing abilities. Acking it as I've done is
all I can do. Bug James. :)
-- steve
prev parent reply other threads:[~2013-08-12 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 14:42 [PATCH] hpsa: fix warning with smp_processor_id() in preemptible John Kacur
2013-08-12 13:13 ` Sebastian Andrzej Siewior
2013-08-12 13:33 ` John Kacur
2013-08-12 13:58 ` scameron [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=20130812135845.GA15147@beardog.cce.hp.com \
--to=scameron@beardog.cce.hp.com \
--cc=bigeasy@linutronix.de \
--cc=jbottomley@parallels.com \
--cc=jkacur@redhat.com \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=williams@redhat.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 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.