From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Stephane Grosjean <s.grosjean@peak-system.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: About peak_pci PATH v6.1
Date: Mon, 20 Feb 2012 13:18:54 +0100 [thread overview]
Message-ID: <4F423A2E.3030806@pengutronix.de> (raw)
In-Reply-To: <4F422DA4.1080703@peak-system.com>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
On 02/20/2012 12:25 PM, Stephane Grosjean wrote:
> I found that the i2c_transfer() is able to sleep, which is generally
> *not* a good idea when in an interrupt context...
Not allowed :)
> So, I changed the delay management with a delayed work mechanism. I
> successfully tested the change on my testbed, but as you know, this is
> not the best place for testing...
> I hope you will be able to find some time to test that new patch.
>
> @Marc: the peak_pci and peak_pcmcia patches bring modifications to the
> can/sja1000 dir Kconfig and Makefile, So the apply sequence order is
> critical (I mean, the peak_pci patch must be applied before the
> peak_pcmcia, because of lines numbers). How to fix that? I first
> proposed to use a serie of patches but this was not approved...
I think due to my too short answer there was a misunderstanding. IIRC in
one patch you 1. fixed a problem (which is already in mainline) and 2.
introduced a new feature. This is why I asked for separate patches. All
changes can still go into a series.
I already added your "add support for PEAK-System PCIe/PCIeC/miniPCI
cards" patch to can-next/master, but If you now have a better version,
I'll force update the branch.
I just updated can-next/master, so that it doesn't include your patch.
Now it get complicated :) In order to test the patches you need Olivers
unplug fix patch, I send it to David today, and it's not part of
can-next, yet. For easy testing, I merged linux-can into linux-can-next,
the branch is called "with-can-merge" in the linux-can-next repo. Please
make your patch series based on that branch, I'll apply it to
linux-can-next/master and ask David to merge net into net-next first, in
case he hasn't.
Back to your question. Yes, please give us a series of patches, even if
its PCI and USB drivers.
I hope you understand what I mean ;)
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-20 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 11:25 About peak_pci PATH v6.1 Stephane Grosjean
2012-02-20 12:18 ` Marc Kleine-Budde [this message]
2012-02-20 13:25 ` Stephane Grosjean
2012-02-23 15:28 ` Stephane Grosjean
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=4F423A2E.3030806@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=s.grosjean@peak-system.com \
--cc=socketcan@hartkopp.net \
/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).