From: Andries Brouwer <aebr@win.tue.nl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: libata update posted
Date: Sun, 14 Sep 2003 11:12:25 +0200 [thread overview]
Message-ID: <20030914111225.A3371@pclin040.win.tue.nl> (raw)
In-Reply-To: <20030913212849.GB21426@gtf.org>; from jgarzik@pobox.com on Sat, Sep 13, 2003 at 05:28:49PM -0400
On Sat, Sep 13, 2003 at 05:28:49PM -0400, Jeff Garzik wrote:
> On Sat, Sep 13, 2003 at 10:56:52PM +0200, J.A. Magallon wrote:
> > The patch for 2.4 kills drivers/char/defkeymap.c.
> > Is this in on purpose ? I think this is autogenerated but not killed
> > in mrproper.
>
> Yep, that's an autogenerated file. I nudge Marcelo to "bk rm" it every now
> and then :) Just remove it from the patch and you'll be ok.
>
> I have to "rm -f drivers/char/defkeymap.c" on occasion, in order to do
> some bk stuff, too.
Long ago it happened every once in a while that I added a key type.
In such a case one got new kernel keyboard headers, had to recompile
loadkeys with the new headers, use that new loadkeys to regenerate
defkeymap.c, and then recompile the kernel.
This shows why defkeymap.c is not generated in the kernel build
but distributed.
Andries
next prev parent reply other threads:[~2003-09-14 9:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 3:23 libata update posted Jeff Garzik
2003-09-13 20:56 ` J.A. Magallon
2003-09-13 21:28 ` Jeff Garzik
2003-09-14 9:12 ` Andries Brouwer [this message]
2003-09-14 17:26 ` Jeff Garzik
2003-09-14 19:38 ` Andries Brouwer
2003-09-14 20:09 ` Jeff Garzik
2003-09-14 21:09 ` Andries Brouwer
2003-09-14 21:36 ` Jeff Garzik
2003-09-14 21:38 ` James Bottomley
2003-09-14 22:18 ` Andries Brouwer
2003-09-16 19:34 ` Pavel Machek
2003-09-13 21:13 ` J.A. Magallon
2003-09-13 21:38 ` Jeff Garzik
2003-09-14 22:27 ` Hugo Mills
2003-09-14 22:31 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-10-05 23:15 Jeff Garzik
2003-10-05 23:41 ` Bartlomiej Zolnierkiewicz
2003-08-13 3:40 Jeff Garzik
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=20030914111225.A3371@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=jamagallon@able.es \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).