From: Borislav Petkov <bp@amd64.org>
To: Rohit Yadav <rohityadav89@gmail.com>
Cc: Borislav Petkov <bp@amd64.org>,
"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Arch: x86: process: Fix a compilation warning.
Date: Mon, 30 May 2011 22:17:11 +0200 [thread overview]
Message-ID: <20110530201711.GA8320@aftab> (raw)
In-Reply-To: <BANLkTikKjjnai0kvvdA9OdBeBhkJWT9=oQ@mail.gmail.com>
On Mon, May 30, 2011 at 03:52:54PM -0400, Rohit Yadav wrote:
> > Yep, all valid points. Another one would be to search whether this got
> > already fixed before wasting effort:
> >
> > http://git.kernel.org/tip/598e887d8b01655780c81cc86a9e7820ed091580
>
> What is the best way to search if something got fixed? There are
> plenty of repositories at git.kernel.org
> I'm using this one:
> http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Well, you either subscribe to lkml and search in your archives for it
or use your favourite search engine - they're usu. indexing lkml pretty
fast.
For example, google already indexed your mail I'm replying to and
returns it as the first result:
http://www.google.com/search?q=rohit+yadav+if+something+got+fixed
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-05-30 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 17:30 [PATCH] Arch: x86: process: Fix a compilation warning Rohit Yadav
2011-05-30 17:40 ` Valdis.Kletnieks
2011-05-30 17:58 ` Rohit Yadav
2011-05-30 18:11 ` Valdis.Kletnieks
2011-05-30 18:22 ` Borislav Petkov
2011-05-30 19:52 ` Rohit Yadav
2011-05-30 20:00 ` Randy Dunlap
2011-05-30 20:21 ` Borislav Petkov
2011-05-30 20:17 ` Borislav Petkov [this message]
2011-05-30 23:22 ` Jesper Juhl
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=20110530201711.GA8320@aftab \
--to=bp@amd64.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rohityadav89@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.