From: Greg KH <greg@kroah.com>
To: johnlinn@comcast.net
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
alan@lxorguk.ukuu.org.uk,
michal simek <michal.simek@petalogix.com>,
joe@perches.com, grant likely <grant.likely@secretlab.ca>,
John Linn <john.linn@xilinx.com>
Subject: Re: [PATCH V5] tty/serial: add support for Xilinx PS UART
Date: Fri, 29 Apr 2011 18:23:24 -0700 [thread overview]
Message-ID: <20110430012324.GA12003@kroah.com> (raw)
In-Reply-To: <297990190.2103989.1304125884176.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
On Sat, Apr 30, 2011 at 01:11:24AM +0000, johnlinn@comcast.net wrote:
>
> > On Sat, Apr 30, 2011 at 12:15:54AM +0000, johnlinn@comcast.net wrote:
> > >
> > > > On Fri, Apr 29, 2011 at 03:59:06PM -0600, johnlinn@comcast.net
> > wrote:
> > > > > From: John Linn <john.linn@xilinx.com>
> > > > >
> > > > > The Xilinx PS Uart is used on the new ARM based SoC. This
> > > > > UART is not compatible with others such that a seperate
> > > > > driver is required.
> > > > >
> > > > > Signed-off-by: John Linn <john.linn@xilinx.com>
> > > >
> > > > That's fine, but:
> > > >
> > > > >
> > > > > This email and any attachments are intended for the sole use of
> > the
> > > > named recipient(s) and contain(s) confidential information that
> > may be
> > > > proprietary, privileged or copyrighted under applicable law. If
> > you
> > > > are not the intended recipient, do not read, copy, or forward
> > this
> > > > email message or any attachments. Delete this email message and
> > any
> > > > attachments immediately.
> > > > >
> > > >
> > > > That means I can't apply this patch :(
> > > >
> > > > {sigh}
> > > >
> > > > Please fix this, as it does not allow you to participate in
> > kernel
> > > > development efforts.
> > >
> > > Sorry for trying your patience, V6 is out and shouldn't have that
> > > nasty issue.
> > >
> > > Your patience is much appreciated as I'm fighting the good fight
> > with
> > > legal about this and working around it (not real smooth obviously).
> >
> > You need to do what everyone else does in this situation (Intel,
> > Microsoft, IBM, etc.) and set up a Linux email server somewhere in
> > your
> > company and use it instead, to get your patches out and participate
> > properly in the Linux kernel community.
> >
> > Sadly, it's quite common to have to do this :(
>
> I will work on the issue, but since this is ready to go in, I'm going to resend
> V6 from home later if possible to avoid the BS.
>
> Again, my apologies, I didn't realize it was doing this all along.
>
> My bosses are asking if there's anything specific in that crap that is the offending
> part such that part of it can be left?
None of it can be left, sorry.
> I owe you some beer sometime for sure.
I will be glad to take you up on it :)
greg k-h
prev parent reply other threads:[~2011-04-30 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 21:59 [PATCH V5] tty/serial: add support for Xilinx PS UART johnlinn
2011-04-29 23:37 ` Greg KH
2011-04-30 0:15 ` johnlinn
2011-04-30 0:27 ` Greg KH
2011-04-30 1:11 ` johnlinn
2011-04-30 1:23 ` Greg KH [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=20110430012324.GA12003@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grant.likely@secretlab.ca \
--cc=joe@perches.com \
--cc=john.linn@xilinx.com \
--cc=johnlinn@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@petalogix.com \
/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