From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI fixes for 2.6.27-rc1
Date: Mon, 04 Aug 2008 09:44:52 -0500 [thread overview]
Message-ID: <1217861092.3318.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20080804142927.GG8301@fluff.org.uk>
On Mon, 2008-08-04 at 15:29 +0100, Ben Dooks wrote:
> On Sun, Aug 03, 2008 at 05:03:05PM -0500, James Bottomley wrote:
> > This is just a small selection of four fixes, one expanding driver
> > bindings and the other three fixing actual bugs (all of which need
> > backporting to 2.6.26 I'm afraid).
> >
> > The patch is available here:
> >
> > master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-rc-fixes-2.6.git
> >
> > The short changelog is:
> >
> > HighPoint Linux Team (1):
>
> I thought group (or non-person) submissions where explicitly
> prohibitted in the signoff section in Documentation/SubmittingPatches
Not as I read it. It says:
then you just add a line saying
Signed-off-by: Random J Developer
<random@developer.example.org>
using your real name (sorry, no pseudonyms or anonymous
contributions.)
Which doesn't preclude company signoffs (as long as it's a real
company). Of course, most companies worry about the legal liability
from the GPL and the DCO, which is why we get so few of them.
James
prev parent reply other threads:[~2008-08-04 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 22:03 [GIT PATCH] SCSI fixes for 2.6.27-rc1 James Bottomley
2008-08-04 14:29 ` Ben Dooks
2008-08-04 14:15 ` Alan Cox
2008-08-04 21:11 ` Jeff Garzik
2008-08-04 14:44 ` James Bottomley [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=1217861092.3318.10.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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