linux-kernel - Re: [PATCH v4:No Change] xHCI:Fixing xhci

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130903081710.GE6329@mwanda>
Date:	Tue, 3 Sep 2013 11:17:10 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Kumar Gaurav <kumargauravgupta3@...il.com>
Cc:	sarah.a.sharp@...ux.intel.com, gregkh@...uxfoundation.org,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v4:No Change] xHCI:Fixing xhci_readl definition and
 function call

On Tue, Sep 03, 2013 at 08:59:59AM +0530, Kumar Gaurav wrote:
> I tried applying this patch on linux-next and it applies well.
> i used
>     git apply --apply
> 

The merge window is open.  No one is applying patches until -rc1 comes
out.

This one is not redone in the right way.  The subject is wrong:

 Bad: [PATCH v4:No Change] xHCI:Fixing xhci_readl definition and function call
Good: [PATCH v4] xHCI: Fixing xhci_readl definition and function call

There should be a note under the --- line to say what changed and why
you are resending.  It's not helpful to say "No Change" because actually
there were many changes.

---
v4: Update to apply on linux-next.

regards,
dan carpenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/