From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
chris.mason@oracle.com, handygewinnspiel@gmx.de, matthew@wil.cx,
rjw@sisk.pl, HWerner4@gmx.de, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
mchehab@infradead.org, stable@kernel.org,
Christoph Hellwig <hch@lst.de>, Lachlan McIlroy <lachlan@sgi.com>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?
Date: Sun, 18 Jan 2009 17:06:57 -0500 [thread overview]
Message-ID: <20090118220657.GA14814@infradead.org> (raw)
In-Reply-To: <496E5DB8.1030007@sandeen.net>
On Wed, Jan 14, 2009 at 03:48:40PM -0600, Eric Sandeen wrote:
> > This patch applies OK to 2.6.27 and 2.6.28. Is it also needed there?
> > If so, it should have had "Cc: <stable@kernel.org>" in the changelog so
> > that it doesn't get lost.
> >
>
> It is needed for .28, but should not be needed for .27 AFAIK.
That's correct.
next prev parent reply other threads:[~2009-01-18 22:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090112190420.51f75853@pedra.chehab.org>
[not found] ` <20090112132130.6c932b85.akpm@linux-foundation.org>
[not found] ` <20090112220624.4fbfee34@pedra.chehab.org>
[not found] ` <20090112162337.318dd61d.akpm@linux-foundation.org>
2009-01-13 18:47 ` handygewinnspiel
2009-01-13 18:59 ` Andrew Morton
2009-01-13 19:17 ` handygewinnspiel
2009-01-13 19:37 ` Andrew Morton
2009-01-13 20:02 ` handygewinnspiel
2009-01-13 20:38 ` Matthew Wilcox
2009-01-14 18:29 ` Chris Mason
2009-01-14 21:19 ` wk
2009-01-14 21:24 ` Chris Mason
2009-01-14 21:35 ` Eric Sandeen
2009-01-14 21:40 ` Chris Mason
2009-01-14 23:00 ` Kay Sievers
2009-01-15 1:54 ` Chris Mason
2009-01-14 21:41 ` Eric Sandeen
2009-01-14 21:44 ` Andrew Morton
2009-01-14 21:48 ` Eric Sandeen
2009-01-14 22:57 ` Lachlan McIlroy
2009-01-18 22:06 ` Christoph Hellwig [this message]
2009-01-14 21:41 ` wk
2009-01-14 22:30 ` Dave Chinner
2009-01-15 19:41 ` wk
2009-01-15 22:23 ` Dave Chinner
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=20090118220657.GA14814@infradead.org \
--to=hch@infradead.org \
--cc=HWerner4@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=handygewinnspiel@gmx.de \
--cc=hch@lst.de \
--cc=lachlan@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mchehab@infradead.org \
--cc=rjw@sisk.pl \
--cc=sandeen@sandeen.net \
--cc=stable@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs@oss.sgi.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
Powered by JetHome