From: Piotr Hosowicz <piotr@hosowicz.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: The horror is over, but I deleted and forgot some lines - please help
Date: Thu, 05 Aug 2010 17:19:16 +0200 [thread overview]
Message-ID: <4C5AD674.30908@example.com> (raw)
Hello,
I git-synchronized linux kernel source but it failed to build. I
discovered that the problem is in sound/pci/hda/hda_codec.c . There was
some git specific line of text, so I just deleted it and some other two
lines. It failed again because one of the lines that I just deleted
contained trailing { brace, closing for statement as far as I remember.
Can somebody remind me what had I deleted at first? And how to spot such
situations in the future? I thought that I could write a script to
search and i.e. grep *.c files in the source to catch such coliding
places. But I don't know what should I search.
Reagrds,
Piotr Hosowicz
PS: With working sound ;-)
--
Na przyjęciu chłopak pyta blondynkę:
- Czy mogę cię prosić do walca?
- Zgłupiałeś? To już nie miałeś czym przyjechać?
NP: Peter Green Splinter Group - Turn Your Love Away
NB: 2.6.35-20100805-1436+
next reply other threads:[~2010-08-05 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 15:19 Piotr Hosowicz [this message]
2010-08-07 13:29 ` The horror is over, but I deleted and forgot some lines - please help Piotr Hosowicz
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=4C5AD674.30908@example.com \
--to=piotr@hosowicz.com \
--cc=linux-kernel@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 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.