public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	John David Anglin <dave.anglin@bell.net>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Mikulas Patocka <mpatocka@redhat.com>,
	stepanm@codeaurora.org, Thomas Gleixner <tglx@linutronix.de>,
	deller@gmx.de, dhowells@redhat.com,
	yasutake.koichi@jp.panasonic.com, eike-kernel@sf-tec.de,
	linux-parisc@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.4-rc7
Date: Tue, 15 May 2012 20:04:39 +0100	[thread overview]
Message-ID: <1337108679.3005.34.camel@dabdike.lan> (raw)
In-Reply-To: <4FB2A43D.7090005@linux.vnet.ibm.com>

On Wed, 2012-05-16 at 00:15 +0530, Srivatsa S. Bhat wrote:
> On 05/16/2012 12:12 AM, Linus Torvalds wrote:
> 
> > On Tue, May 15, 2012 at 11:29 AM, Srivatsa S. Bhat
> > <srivatsa.bhat@linux.vnet.ibm.com> wrote:
> >>>
> >>> Can somebody send the final patches with proper subject lines etc,
> >>> instead of hiding them in unrelated threads? I hate picking up patches
> >>> that I don't personally know from the middle of some random thread.
> >>>
> >>
> >>
> >> Okay, here they are:
> > 
> > What part of "with proper subject lines" didn't you get?
> > 
> > Look at the subject line. Look at how you put the patch in the middle
> > of an old thread that was about something totally different.
> > 
> > This was *exactly* what I complained about. I don't want patches like this.
> > 
> 
> 
> Oops! Sorry about that! I will resend in a separate thread with appropriate
> subject line.

If it helps, I've already imported it to the parisc fixes tree with a
corrected subject line.  We still have this and the PA1.1 fix, when I
can confirm it's actually the complete fix for the boot panics.

James



  reply	other threads:[~2012-05-15 19:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13  2:04 Linux 3.4-rc7 Linus Torvalds
2012-05-13 19:56 ` Srivatsa S. Bhat
2012-05-13 20:08   ` John David Anglin
2012-05-13 20:28     ` Srivatsa S. Bhat
2012-05-13 20:40       ` John David Anglin
2012-05-14  0:42         ` John David Anglin
2012-05-15 17:24           ` Linus Torvalds
2012-05-15 18:29             ` Srivatsa S. Bhat
2012-05-15 18:39               ` Srivatsa S. Bhat
2012-05-15 18:42               ` Linus Torvalds
2012-05-15 18:45                 ` Srivatsa S. Bhat
2012-05-15 19:04                   ` James Bottomley [this message]
2012-08-02  1:00           ` Mikulas Patocka
2012-08-02  1:47             ` John David Anglin
2012-08-07 18:41               ` Mikulas Patocka
2012-08-07 19:00                 ` John David Anglin
2012-05-13 20:30   ` Tobias Ulmer

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=1337108679.3005.34.camel@dabdike.lan \
    --to=james.bottomley@hansenpartnership.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=dhowells@redhat.com \
    --cc=eike-kernel@sf-tec.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=stepanm@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yasutake.koichi@jp.panasonic.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