From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [PATCH 4/6] SPI: S3C64XX: Check before mem-region release Date: Thu, 21 Jan 2010 08:00:11 -0700 Message-ID: References: <1263808215-16544-1-git-send-email-jassisinghbrar@gmail.com> <1263808215-16544-4-git-send-email-jassisinghbrar@gmail.com> <1b68c6791001181542p618a8d47n45a120e51cfed1f1@mail.gmail.com> <1b68c6791001190152m652fd117k468893144af8dcfe@mail.gmail.com> <1b68c6791001201735w3060c54blfa85b547917727c2@mail.gmail.com> <1b68c6791001201746p313234bbkdf5fe5db0dcecd9f@mail.gmail.com> <1b68c6791001201906r45c52f71h7f5ea396e91ef3b8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, patchwork , spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Jeremy Kerr , ben-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org To: jassi brar Return-path: In-Reply-To: <1b68c6791001201906r45c52f71h7f5ea396e91ef3b8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: spi-devel-general-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-spi.vger.kernel.org On Wed, Jan 20, 2010 at 8:06 PM, jassi brar wrot= e: > On Thu, Jan 21, 2010 at 11:55 AM, Grant Likely > wrote: >> On Wed, Jan 20, 2010 at 6:46 PM, jassi brar w= rote: >>> On Thu, Jan 21, 2010 at 10:35 AM, jassi brar = wrote: >>>> Hi Grant Likely, >>>> =A0You have reviewed this series of patches but didn't ACK/NAK. >>>> Could you kindly confirm if u accept them or want some changes? >>>> Thanks. >>> Nevermind, I just saw ur ACK at my official ID (many maintainers reply >>> something like >>> 'pulled now' to the patch thread but thats ok if you ACK personally). >>> Thanks. >> >> I'm using patchwork.kernel.org for collecting spi patches. >> Unfortunately patchwork doesn't provide any mechanism for emailing >> "merged" messages when I accept patches. =A0To compensate, I've started >> cc'ing patch authors my next- branch update message when I push out an >> updated tree. >> >> You can also always look at patchwork.kernel.org to see if your >> patches are still in the queue. =A0I won't forget accidentally drop any >> patches tracked by patchwork. > well, it might not just be the submitter, but also others in the thread > interested in knowing the fate of a particular patch. And having to > poll some repo for that, isn't very efficient. It's not important to be n= otified > _when_ you accept the patch, but only _if_ you accept, which I think > you would know after seeing the patch and/or some further clarifications > from the submitter. Since I review patches on patchwork, I don't have an easy link between what I'm picking up and my email client. Only when I need to comment on something will I actually go and find the thread in my mailer. So it is considerably less efficient for me to go and reply to every patch submission. Jeremy, would it be possible to have a way of sending out a status update email from within patchwork? Thanks, g. -- = Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. ---------------------------------------------------------------------------= --- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Confere= nce attendees to learn about information security's most important issues throu= gh interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev