public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Alexey Dobriyan <adobriyan@sw.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc3-mm1: cannot stat `vdso.so.dbg'
Date: Thu, 23 Aug 2007 01:57:48 +0200	[thread overview]
Message-ID: <200708230157.48526.ak@suse.de> (raw)
In-Reply-To: <20070822231632.9A7D54D0418@magilla.localdomain>

On Thursday 23 August 2007 01:16:32 Roland McGrath wrote:
> > How come they have identical subjects and identical description? How is 
> > anybody supposed to make sense of this?
> 
> Sorry, I asked Andrew and he said to send replacement patches.
> I thought I was following instructions.

The problem is they're two patching consecutively patching the same
file with 100% identical subject/description.

So either: they should be merged together into one patch
or the second (or first) needs a new description/subject

I right now got the second as 

vdso-do-something-more-with-unstripped-copies-on-disk:

Do something with vdsos and debug information

From: Roland McGrath <roland@redhat.com>

TBD this needs a proper changelog/subject from Roland. I have no idea what 
it does


But clearly that's not an satisfactionary state. Which of the
options do you prefer?

-Andi



  reply	other threads:[~2007-08-22 23:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 10:15 2.6.23-rc3-mm1: cannot stat `vdso.so.dbg' Alexey Dobriyan
2007-08-22 10:24 ` Roland McGrath
2007-08-22 15:36   ` Andrew Morton
2007-08-22 21:56     ` Roland McGrath
2007-08-22 22:58       ` Andi Kleen
2007-08-22 23:16         ` Roland McGrath
2007-08-22 23:57           ` Andi Kleen [this message]
2007-08-23  0:32             ` Roland McGrath

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=200708230157.48526.ak@suse.de \
    --to=ak@suse.de \
    --cc=adobriyan@sw.ru \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox