From: Stephen Rothwell <sfr@canb.auug.org.au>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 29
Date: Wed, 29 Dec 2010 21:00:45 +1100 [thread overview]
Message-ID: <20101229210045.f583c18d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <AANLkTimHgKKw8eeH==YYY_Z9keewxamfOpRzLVDgKxv6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
Hi Sedat,
On Wed, 29 Dec 2010 10:54:28 +0100 Sedat Dilek <sedat.dilek@googlemail.com> wrote:
>
> What is the recommended way in case of these "comparison" warnings?
> Send to whom/where?
Their respective maintainers (see scripts/get_maintainer.pl), unless you
can also identify the commit that introduced the warning, then you should
also cc author(s),
Thanks
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-12-29 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 2:07 linux-next: Tree for December 29 Stephen Rothwell
2010-12-29 6:41 ` Anca Emanuel
2010-12-29 8:58 ` Anca Emanuel
2010-12-29 9:46 ` Stephen Rothwell
2010-12-29 10:45 ` Anca Emanuel
2010-12-29 13:08 ` Mark Brown
2010-12-29 9:54 ` Sedat Dilek
2010-12-29 10:00 ` Stephen Rothwell [this message]
2010-12-29 16:53 ` linux-next: Tree for December 29 (netfilter build errors) Randy Dunlap
2010-12-30 2:10 ` Shan Wei
2010-12-30 2:18 ` Changli Gao
2010-12-30 16:47 ` Sedat Dilek
2010-12-30 17:07 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 0:28 linux-next: Tree for December 29 Stephen Rothwell
2008-12-29 16:16 Stephen Rothwell
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=20101229210045.f583c18d.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.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