All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: roz <oroz3x@gmail.com>
Cc: driverdev-devel@linuxdriverproject.org
Subject: Re: [PATCH v4] ks7010: enclose non-trivial defines in parentheses
Date: Thu, 18 Feb 2021 19:34:40 +0100	[thread overview]
Message-ID: <YC6zQJzUwn1cgai2@kroah.com> (raw)
In-Reply-To: <A1MQOQ.EDMUBBX5O0OU1@gmail.com>

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Thu, Feb 18, 2021 at 11:59:34PM +0530, roz wrote:
> Hi,
> 
> I wanted to check the status on the following patch.
> I wanted the result for eudyptula task 10 submission.

There's no deadlines here, and the first rule of the eudyptula challenge
is that you can not talk about the eudyptula challenge without getting
in trouble :(

> It would be great if i can check if the mail is being
> processed or rejected. I appologise for any troubles.

I rejected it a while ago, you got the email from my patch bot, right?
See here:
	https://lore.kernel.org/r/YCY2FTmycppYXY0O@kroah.com

Why did you resend it if you didn't do what that email said to do?

thanks,

greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

      reply	other threads:[~2021-02-18 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 13:27 [PATCH v4] ks7010: enclose non-trivial defines in parentheses shivang upadhyay
2021-02-18 18:29 ` roz
2021-02-18 18:34   ` 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=YC6zQJzUwn1cgai2@kroah.com \
    --to=greg@kroah.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=oroz3x@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.