From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: unsigned commits
Date: Mon, 6 Dec 2010 23:34:58 +0000 [thread overview]
Message-ID: <20101206233458.GA3738@srcf.ucam.org> (raw)
In-Reply-To: <20101207103346.fbbcf099.sfr@canb.auug.org.au>
On Tue, Dec 07, 2010 at 10:33:46AM +1100, Stephen Rothwell wrote:
> Hi Matthew,
>
> Looking through the drivers-x86 tree update for linux-next today, I found
> a few commits that have no signed-off-by line ...
>
> 8f2e88b22a4caaebcc8d5a9e00a8249fec350cf3 "Generic key reporting"
> e3a2b10707902bcf95d022a5bab8f13b26bccc64 "ACPI-ify"
> 52f4e59f269e0d3bb1d54ca654d9cbf6880e7370 "Fix some tos1900 devices"
> 64ea4efdd949c99d9206a44a43984d2e861350f1 "wwan rfkill stubs"
>
> And I think those commit messages could do with some elaboration as well.
They're somewhat WIP - I'll shift them to a topic branch.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-12-06 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 23:33 linux-next: unsigned commits Stephen Rothwell
2010-12-06 23:34 ` Matthew Garrett [this message]
2010-12-06 23:38 ` Stephen Rothwell
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=20101206233458.GA3738@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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