From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: umesh jaiswal <umesh_j123@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to know to which file in kernel the patch can be applied?
Date: Fri, 31 Aug 2001 13:20:36 +0200 [thread overview]
Message-ID: <3B8F7304.33BAE89A@loewe-komp.de> (raw)
In-Reply-To: <F78EdcWCJ2geAvaFI7J00002fb5@hotmail.com>
umesh jaiswal wrote:
>
> Dear sir ...
> I have applied a linux-2_2_16_diff.htm patch which I have downloaded
> from kgdb site for remote kernel debugging by giving the command
> cd /usr/src/linun2.2.16
> $[linux] patch p0 < linux-2_2_16_diff.htm
>
> But after appling the above patch command the console giving the massage :
> type the file name you want to patch.
> I don't know sir which file I have to patch for remote kernel debugging
> support on my development machine .pls help me out.
>
Most of the patches assume that your current working directory is
/usr/src
If you are in /usr/src/linux* try "patch -p1 <patch"
You can browse the patch with less and see at the "diff" line what
the expected hierachy looks like
prev parent reply other threads:[~2001-08-31 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 9:53 how to know to which file in kernel the patch can be applied? umesh jaiswal
2001-08-31 11:20 ` Peter Wächtler [this message]
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=3B8F7304.33BAE89A@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=linux-kernel@vger.kernel.org \
--cc=umesh_j123@hotmail.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