From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: linux 2.6.34 bug
Date: Thu, 8 Jul 2010 21:22:30 +0200 [thread overview]
Message-ID: <20100708192230.GA27952@pengutronix.de> (raw)
In-Reply-To: <201007081842.16347.marek.vasut@gmail.com>
Hello,
On Thu, Jul 08, 2010 at 06:42:16PM +0200, Marek Vasut wrote:
> Dne ?t 8. ?ervence 2010 17:36:21 dylan cristiani napsal(a):
> > Hi Marek,
> > we were in touch few moths ago about a ucb1400 touchscreen, issue if you
> > remember: you sent me a patch to pass the platform specific codec irq,
> > through ucb1400_pdata; after that i went from 3.6.32 to 2.6.34 and
> > i noticed that your patch was into mainline; in this kernel, related to
> > the ucb1400 codec again, i noticed one bug about the ac97 codec reset
> > that is bulverde platform specific: i don't know hot to submit a patch
> > and to whom to submit it, so i bother, you sorry in advance....; in
> > particular: in new kernel the function
> > "void pxa27x_assert_ac97reset(int reset_gpio, int on)"
> > has been moved to arch/arm/mach-pxa/pxa27x.c file:
>
> CCing linux-arm-kernel and Eric.
>
> btw. to submit patch :
>
> git add <list of changed files>
>
> git commit -s
> <editor will pop up, type the commit message>
>
> git log # here check the hash of the last commit before yours
>
> git send-email --to="linux-arm-kernel at lists.infradead.org" --
> cc="eric.y.miao at gmail.com" --cc="marek.vasut at gmail.com" <the hash from previous
> step>
>
> That's probably the easiest way :)
No. Instead of checking the hash of the last commit via git log, you
can simply pass "HEAD~1" instead of the actual hash.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-07-08 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100708173621.00003527@unknown>
2010-07-08 16:42 ` linux 2.6.34 bug Marek Vasut
2010-07-08 19:22 ` Uwe Kleine-König [this message]
2010-07-13 1:50 ` Eric Miao
2010-07-13 10:44 ` Dylan Cristiani
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=20100708192230.GA27952@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).