From: Frank Pavlic <fpavlic@de.ibm.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/5] s390: qeth driver fixes
Date: Tue, 9 Jan 2007 14:39:22 +0100 [thread overview]
Message-ID: <20070109133922.GA21804@de.ibm.com> (raw)
In-Reply-To: <45A342EB.2020200@pobox.com>
Sorry for the trouble and also thank you very much
for having done the extra work. I made the patches
using git-format-patch so seems that I have to review
them more carefully or I still haven't understand to use
git-format-patch properly.
In any case I will read the documents you mentioned
once again to keep such points in mind...
Frank
On Tue, Jan 09, 2007 at 02:23:23AM -0500, Jeff Garzik wrote:
> Frank Pavlic wrote:
> >Hi ,
> >
> >please apply following 5 patches for s390 network device drivers.
> >Sorry for the fifth patch containing some lines which just remove
> >whitespaces. Another patch will follow in the next couple of days
> >with more whitespace and coding style cleanups in drivers/s390/net.
> >
> >Thank you
> >
> >Frank
> >
> >[PATCH 1/5] s390: qeth driver fixes
> >
> >From: Frank Blaschka <Frank.Blaschka@de.ibm.com>
> >From: Ursula Braun <braunu@de.ibm.com>
> > - VLAN header reordering did not work on packets
> > received through qeth interface in layer 2 mode.
> > This caused dhcpcd not to work with VLAN devices.
> > - set qeth performance statistics initally inactive
> >
> >Signed-off-by: Frank Pavlic <fpavlic@de.ibm.com>
>
> applied patches 1-4 of 5. patch #5 failed to apply, and also, it's not
> really appropriate for the current release candidate bugfix window.
>
> Also:
>
> 1) Please include notes to me and reviewers following the "---" marker.
> Everything before the "---" is copied /verbatim/ into the kernel
> changelog. Everything after "---", except the patch itself, is ignored.
>
> I had to hand-edit each of your patches, to remove the "Hi , ... Frank"
> paragraph and the "[PATCH 1/5] S390: ..." from the body of each email.
>
> 2) Your subject line should be more descriptive. The subject line is
> used to generate a one-line summary. You can see how your subject lines
> are vague:
>
> [PATCH] s390: qeth driver fixes
> [PATCH] s390: qeth driver fixes
> [PATCH] s390: qeth driver fixes
>
> Here, I had to hand-edit each email subject line to be more descriptive.
>
> 3) In general, review Documentation/SubmittingPatches and
> http://linux.yyz.us/patch-format.html
>
> Jeff
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-01-09 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 16:29 [PATCH 1/5] s390: qeth driver fixes Frank Pavlic
2007-01-09 7:23 ` Jeff Garzik
2007-01-09 13:39 ` Frank Pavlic [this message]
2007-01-09 13:45 ` 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=20070109133922.GA21804@de.ibm.com \
--to=fpavlic@de.ibm.com \
--cc=jgarzik@pobox.com \
--cc=netdev@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).