From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Олег Мороз" <oleg.moroz@mcc.vniiem.ru>
Cc: linux-can@vger.kernel.org
Subject: Re: plx_pci.c patch
Date: Fri, 27 Dec 2013 16:21:08 +0100 [thread overview]
Message-ID: <52BD9AE4.7010104@hartkopp.net> (raw)
In-Reply-To: <52B88A9E.6000008@mcc.vniiem.ru>
Hello Oleg,
thanks for your contribution!
On 23.12.2013 20:10, Олег Мороз wrote:
>
> Hello. I've added the ELCUS CAN-200-PCI card support into sja1000_plx_pci
> driver. Could you please review my changes and commit it to the Linux kernel
> repository?
>
Please post patches always in-line, e.g. an example for plx_pci.c is this
commit:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/can/sja1000/plx_pci.c?id=e4bc6c06569a90512169d98a11b3eb2ec18da4ae
Which had this patch:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/drivers/net/can/sja1000/plx_pci.c?id=e08534b57e79fa722e3136b79868a725a8eea0f0
And this post on the mailing list:
http://marc.info/?l=linux-netdev&m=132368716608087&w=2
Please sent your patch the same way with a proper Signed-off-by: statement
(preferably without cyrillic characters).
Please clean up your code changes before => remove the line changes below!
Best regards,
Oliver
@@ -440,13 +462,14 @@ static void plx_pci_reset_marathon(struc
}
}
+
+
(why did you introduce these lines?)
static void plx_pci_del_card(struct pci_dev *pdev)
{
struct plx_pci_card *card = pci_get_drvdata(pdev);
struct net_device *dev;
struct sja1000_priv *priv;
int i = 0;
-
(there should remain an empty line)
for (i = 0; i < PLX_PCI_MAX_CHAN; i++) {
dev = card->net_dev[i];
if (!dev)
=> please leave this code as-is. Tnx.
ps. For the entire correct process see:
https://www.kernel.org/doc/Documentation/SubmittingPatches
prev parent reply other threads:[~2013-12-27 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52B8878E.5090505@mcc.vniiem.ru>
2013-12-23 19:10 ` plx_pci.c patch Олег Мороз
2013-12-27 15:21 ` Oliver Hartkopp [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=52BD9AE4.7010104@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=oleg.moroz@mcc.vniiem.ru \
/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.