From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
julia@diku.dk, linux-arm-kernel@lists.infradead.org,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sa1111: Prevent deadlock in resume path
Date: Fri, 11 Jun 2010 00:05:52 +0100 [thread overview]
Message-ID: <20100610230552.GE32362@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201006102349.12849.marek.vasut@gmail.com>
On Thu, Jun 10, 2010 at 11:49:12PM +0200, Marek Vasut wrote:
> Even though my problem was fixed (yeah, sorry Russell, I didn't know
> the patch tracker was updated to support git-send-email), I have a
> question though.
>
> I believe that Kernel-version is unnecessary. Isn't this information already
> encoded in the git-send-emailed patch?
It's there so that gnu patches can be accepted, and the additional
information does help when applying hard to apply patches, particularly
if either the patch has aged or was generated against an old kernel
version.
Not only that, but it was once critical when we had 2.4 and 2.5/2.6
kernel patches going via the patch system.
Last point to make - and it's in similar vain to the KernelVersion
tag - is that it would be useful if people would tag pure fixes which
should be applied to previous kernels with a "Cc: <stable@kernel.org>"
tag along-side the existing sign-offs. That allows the stable
maintainers to automatically pick up on these patches when they're
merged into mainline.
next prev parent reply other threads:[~2010-06-10 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1274901104-22133-1-git-send-email-marek.vasut@gmail.com>
[not found] ` <20100526191425.GD6232@n2100.arm.linux.org.uk>
[not found] ` <201005262115.57282.marek.vasut@gmail.com>
[not found] ` <20100526201824.GA16418@n2100.arm.linux.org.uk>
2010-06-10 13:56 ` Pavel Machek
2010-06-10 21:49 ` Marek Vasut
2010-06-10 23:05 ` Russell King - ARM Linux [this message]
2010-06-11 12:22 ` Catalin Marinas
2010-06-12 5:36 ` Eric Miao
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=20100610230552.GE32362@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=julia@diku.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®