From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Hin-Tak Leung <hintak.leung@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/9] [compat-2.6 and compat-stable] Remove unused code
Date: Tue, 13 Oct 2009 21:10:28 -0700 [thread overview]
Message-ID: <20091014041028.GA14511@kroah.com> (raw)
In-Reply-To: <43e72e890910131718x68a4a80ehc66a4daf2e299c46@mail.gmail.com>
On Tue, Oct 13, 2009 at 05:18:04PM -0700, Luis R. Rodriguez wrote:
> On Tue, Oct 13, 2009 at 5:12 PM, Hin-Tak Leung <hintak.leung@gmail.com> wrote:
> > On Tue, Oct 13, 2009 at 10:12 PM, Hauke Mehrtens <hauke@hauke-m.de> wrote:
> >
> >> The condition #if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,28)) was
> >> added recently because without it openSuse with kernel 2.6.27 will not
> >> compile. OpenSuse backports the tracepoint part into their 2.6.27 kernel.
> >
> > I remember that thread now. It is probably wrong as a matter of policy
> > to incorporate patches for distro kernels with backport bits through.
> > - I am not saying you shouldn't be helpful and provide them - after
> > all, more users == better testing, and no doubt the investigation
> > itself throws more insights on the detailed mechanisms - but it is
> > just that compat-wireless probably should not try to support arbitrary
> > and substantial changes from a vanilla kernel. I know Suse is popular
> > so it is important to support Suse users, but I am wondering if
> > distro-specific changes should be separate or at least, clearly
> > documented.
>
> Not sure why opensuse added round_jiffies_up() to their 2.6.27
> kernels, greg may know better, but since its only once change I'm
> willing to live with what we did to resolve for it.
We added that to the SLE 11 kernel as it was requred for a bunch of
block layer backports to resolve a number of issues that we needed to
do.
Hope this helps explain things,
greg k-h
next prev parent reply other threads:[~2009-10-14 4:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 21:19 [PATCH 0/10] [compat-2.6 and compat-stable] Mostly build fixes Hauke Mehrtens
2009-10-12 21:19 ` [PATCH 1/9] [compat-2.6 and compat-stable] Export round_jiffies_up again Hauke Mehrtens
2009-10-13 19:39 ` Luis R. Rodriguez
2009-10-13 20:07 ` Luis R. Rodriguez
2009-10-12 21:19 ` [compat-stable] fix build with recent mainline kernel Hauke Mehrtens
2009-10-12 21:19 ` [PATCH 2/9] [compat-2.6 and compat-stable] Remove unused code Hauke Mehrtens
2009-10-13 2:32 ` Hin-Tak Leung
2009-10-13 21:12 ` Hauke Mehrtens
2009-10-14 0:12 ` Hin-Tak Leung
2009-10-14 0:18 ` Luis R. Rodriguez
2009-10-14 4:10 ` Greg KH [this message]
2009-10-12 21:19 ` [PATCH 3/9] [compat-2.6] Move trace headers Hauke Mehrtens
2009-10-12 21:19 ` [PATCH 4/9] [compat-2.6] Fix compile bug with kernel 2.6.32 Hauke Mehrtens
2009-10-12 21:19 ` [PATCH 5/9] [compat-2.6] Remove temporary fix Hauke Mehrtens
2009-10-12 21:19 ` [PATCH 6/9] [compat-2.6] Fix build with kernel < 2.6.27 Hauke Mehrtens
2009-10-13 19:56 ` Luis R. Rodriguez
2009-10-12 21:19 ` [PATCH 7/9] [compat-2.6] b44 fix Hauke Mehrtens
2009-10-12 21:19 ` [PATCH 8/9] [compat-2.6] refresh patches Hauke Mehrtens
2009-10-12 21:19 ` [PATCH 9/9] [compat-2.6] Add skb_add_rx_frag to backport Hauke Mehrtens
2009-10-13 20:11 ` [PATCH 0/10] [compat-2.6 and compat-stable] Mostly build fixes Luis R. Rodriguez
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=20091014041028.GA14511@kroah.com \
--to=greg@kroah.com \
--cc=hauke@hauke-m.de \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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;
as well as URLs for NNTP newsgroup(s).